Update README.md
Browse files
README.md
CHANGED
|
@@ -122,8 +122,8 @@ The data fields are the same among all splits:
|
|
| 122 |
- `bug_type`: the type of the bug in `buggy_solution` (one of [`missing logic`, `excess logic`, `value misuse`, `operator misuse`, `variable misuse`, `function misuse`])
|
| 123 |
- `failure_symptoms`: the problem the bug causes (one of [`incorrect output`, `stackoverflow`, `infinite loop`])
|
| 124 |
- `entry_point`: the name of the function
|
| 125 |
-
-
|
| 126 |
-
-
|
| 127 |
- `test`: the unit tests for the problem
|
| 128 |
- `example_test`: additional unit tests different from `test` that could be e.g. provided to the model (these are not used in the paper)
|
| 129 |
- `signature`: the signature of the function
|
|
|
|
| 122 |
- `bug_type`: the type of the bug in `buggy_solution` (one of [`missing logic`, `excess logic`, `value misuse`, `operator misuse`, `variable misuse`, `function misuse`])
|
| 123 |
- `failure_symptoms`: the problem the bug causes (one of [`incorrect output`, `stackoverflow`, `infinite loop`])
|
| 124 |
- `entry_point`: the name of the function
|
| 125 |
+
- `import`: imports necessary for the solution (only present for Go)
|
| 126 |
+
- `test_setup`: imports necessary for the test execution (only present for Go)
|
| 127 |
- `test`: the unit tests for the problem
|
| 128 |
- `example_test`: additional unit tests different from `test` that could be e.g. provided to the model (these are not used in the paper)
|
| 129 |
- `signature`: the signature of the function
|