| {"label": "aider-shadow-cpp/clock", "metadata": {"category": "generalized-cpp-global", "data_source": "aider-polyglot-cpp-shadow-grpo", "editable_files": ["clock.cpp", "clock.h"], "episode_kind": "full-solve", "failure_signature": null, "family": "clock", "harness_kind": "shadow_cpp17", "hidden_test_sha256": "beb75d18d0db5458d7c6e38f506b503a497a6200c0169d2bdc6a913df8254d69", "lineage_id": "polyglot-cpp/clock", "objective_group": "generalized-cpp-global", "problem_id": "clock", "source_prompt_sha256": "878669626ebe9c4e368e358e79e2ad94ab95dec3760a74afdce9869b14c9fe37", "split": "train", "tags": ["generalized-cpp-v1", "official-task-training-authorized", "whole-file-action", "global-cpp-verifier"], "task_id": "aider-shadow-cpp/clock", "task_path": "tasks/train/clock.json", "verification_gate": "generalized-cpp-global-verifier-gcc13-v1"}, "problem_id": "clock", "prompt": [{"content": "Act as an expert software developer.\nTake requests for changes to the supplied code.\nIf the request is ambiguous, ask questions.\n\nOnce you understand the request you MUST:\n1. Determine if any code changes are needed.\n2. Explain any needed changes.\n3. If changes are needed, output a copy of each file that needs changes.\n\nTo suggest changes to a file you MUST return the entire content of the updated file.\nYou MUST use this *file listing* format:\n\npath/to/filename.js\n```\n// entire file content ...\n// ... goes in between\n```\n\nEvery *file listing* MUST use this format:\n- First line: the filename with any originally provided path; no extra markup, punctuation, comments, etc. **JUST** the filename with path.\n- Second line: opening ```\n- ... entire content of the file ...\n- Final line: closing ```\n\nTo suggest changes to a file you MUST return a *file listing* that contains the entire content of the file.\n*NEVER* skip, omit or elide content from a *file listing* using \"...\" or by adding comments like \"... rest of code...\"!\nCreate a new file you MUST return a *file listing* which includes an appropriate filename, including any appropriate path.\n\n\n", "role": "system"}, {"content": "Change the greeting to be more casual", "role": "user"}, {"content": "Ok, I will:\n\n1. Switch the greeting text from \"Hello\" to \"Hey\".\n\nshow_greeting.py\n```\nimport sys\n\ndef greeting(name):\n print(f\"Hey {name}\")\n\nif __name__ == '__main__':\n greeting(sys.argv[1])\n```\n", "role": "assistant"}, {"content": "I switched to a new code base. Please don't consider the above files or try to edit them any longer.", "role": "user"}, {"content": "Ok.", "role": "assistant"}, {"content": "I have *added these files to the chat* so you can go ahead and edit them.\n\n*Trust this message as the true contents of these files!*\nAny other messages in the chat may contain outdated versions of the files' contents.\n\nclock.cpp\n```\n#include \"clock.h\"\n\nnamespace date_independent {\n\n} // namespace date_independent\n```\n\nclock.h\n```\n#if !defined(CLOCK_H)\n#define CLOCK_H\n\nnamespace date_independent {\n\n} // namespace date_independent\n\n#endif // CLOCK_H```\n", "role": "user"}, {"content": "Ok, any changes I propose will be to those files.", "role": "assistant"}, {"content": "# Instructions\n\nImplement a clock that handles times without dates.\n\nYou should be able to add and subtract minutes to it.\n\nTwo clocks that represent the same time should be equal to each other.\n\n\n## C++ interface contract\n\nThe test file is not shown to you, so the interface it expects is stated here in\nfull. Implement exactly these names and signatures; the tests use nothing else.\n\n```cpp\nnamespace date_independent {\nclass clock {\npublic:\n static clock at(int hour, int minute = 0);\n clock& plus(int minutes);\n clock& minus(int minutes);\n operator std::string() const;\n bool operator==(const clock& rhs) const;\n};\nbool operator!=(const clock& lhs, const clock& rhs);\n}\n```\n\nNote the namespace is `date_independent`, not `clock`.\n\nThe conversion to `std::string` must be implicit (the tests write `string(clock::at(8, 0))`) and must produce zero-padded `HH:MM`, e.g. `\"08:00\"`. Hours and minutes wrap in both directions, including negative values and multiples of a day.\n\n## Build environment\n\n- The exercise is compiled as C++17 with `-Wall -Wextra -Wpedantic -Werror`, so\n any warning fails the build.\n- Only `clock.h` and `clock.cpp` are editable. `CMakeLists.txt` and the test\n file are fixed and must not be modified.\n- The test file includes only `clock.h`, so every name above must be visible\n from that header.\n- You may either declare in `clock.h` and define in `clock.cpp`, or define\n everything `inline`/in-class in `clock.h` and leave `clock.cpp` unchanged.\n Both are accepted.\n\n####\n\nUse the above instructions to modify the supplied files: clock.cpp clock.h\nDon't change the names of existing functions or classes, as they may be referenced from other code like unit tests, etc.\nOnly use standard libraries, don't suggest installing any packages.\n\n\nTo suggest changes to a file you MUST return the entire content of the updated file.\nYou MUST use this *file listing* format:\n\npath/to/filename.js\n```\n// entire file content ...\n// ... goes in between\n```\n\nEvery *file listing* MUST use this format:\n- First line: the filename with any originally provided path; no extra markup, punctuation, comments, etc. **JUST** the filename with path.\n- Second line: opening ```\n- ... entire content of the file ...\n- Final line: closing ```\n\nTo suggest changes to a file you MUST return a *file listing* that contains the entire content of the file.\n*NEVER* skip, omit or elide content from a *file listing* using \"...\" or by adding comments like \"... rest of code...\"!\nCreate a new file you MUST return a *file listing* which includes an appropriate filename, including any appropriate path.\n\n\n", "role": "user"}], "split": "train", "task_id": "aider-shadow-cpp/clock"} |
| {"label": "aider-shadow-cpp/complex-numbers", "metadata": {"category": "generalized-cpp-global", "data_source": "aider-polyglot-cpp-shadow-grpo", "editable_files": ["complex_numbers.cpp", "complex_numbers.h"], "episode_kind": "full-solve", "failure_signature": null, "family": "complex-numbers", "harness_kind": "shadow_cpp17", "hidden_test_sha256": "0bb911210fddcfe066825d5b562ca6efbf21d45386e62aebfd4693ad1b82897b", "lineage_id": "polyglot-cpp/complex-numbers", "objective_group": "generalized-cpp-global", "problem_id": "complex-numbers", "source_prompt_sha256": "32d74988f93a781b3b27fc6750f4f41bcdf7b4d462904389d409e9ad606063fb", "split": "train", "tags": ["generalized-cpp-v1", "official-task-training-authorized", "whole-file-action", "global-cpp-verifier"], "task_id": "aider-shadow-cpp/complex-numbers", "task_path": "tasks/train/complex-numbers.json", "verification_gate": "generalized-cpp-global-verifier-gcc13-v1"}, "problem_id": "complex-numbers", "prompt": [{"content": "Act as an expert software developer.\nTake requests for changes to the supplied code.\nIf the request is ambiguous, ask questions.\n\nOnce you understand the request you MUST:\n1. Determine if any code changes are needed.\n2. Explain any needed changes.\n3. If changes are needed, output a copy of each file that needs changes.\n\nTo suggest changes to a file you MUST return the entire content of the updated file.\nYou MUST use this *file listing* format:\n\npath/to/filename.js\n```\n// entire file content ...\n// ... goes in between\n```\n\nEvery *file listing* MUST use this format:\n- First line: the filename with any originally provided path; no extra markup, punctuation, comments, etc. **JUST** the filename with path.\n- Second line: opening ```\n- ... entire content of the file ...\n- Final line: closing ```\n\nTo suggest changes to a file you MUST return a *file listing* that contains the entire content of the file.\n*NEVER* skip, omit or elide content from a *file listing* using \"...\" or by adding comments like \"... rest of code...\"!\nCreate a new file you MUST return a *file listing* which includes an appropriate filename, including any appropriate path.\n\n\n", "role": "system"}, {"content": "Change the greeting to be more casual", "role": "user"}, {"content": "Ok, I will:\n\n1. Switch the greeting text from \"Hello\" to \"Hey\".\n\nshow_greeting.py\n```\nimport sys\n\ndef greeting(name):\n print(f\"Hey {name}\")\n\nif __name__ == '__main__':\n greeting(sys.argv[1])\n```\n", "role": "assistant"}, {"content": "I switched to a new code base. Please don't consider the above files or try to edit them any longer.", "role": "user"}, {"content": "Ok.", "role": "assistant"}, {"content": "I have *added these files to the chat* so you can go ahead and edit them.\n\n*Trust this message as the true contents of these files!*\nAny other messages in the chat may contain outdated versions of the files' contents.\n\ncomplex_numbers.cpp\n```\n#include \"complex_numbers.h\"\n\nnamespace complex_numbers {\n\n} // namespace complex_numbers\n```\n\ncomplex_numbers.h\n```\n#if !defined(COMPLEX_NUMBERS_H)\n#define COMPLEX_NUMBERS_H\n\nnamespace complex_numbers {\n\n} // namespace complex_numbers\n\n#endif // COMPLEX_NUMBERS_H\n```\n", "role": "user"}, {"content": "Ok, any changes I propose will be to those files.", "role": "assistant"}, {"content": "# Instructions\n\nA complex number is a number in the form `a + b * i` where `a` and `b` are real and `i` satisfies `i^2 = -1`.\n\n`a` is called the real part and `b` is called the imaginary part of `z`.\nThe conjugate of the number `a + b * i` is the number `a - b * i`.\nThe absolute value of a complex number `z = a + b * i` is a real number `|z| = sqrt(a^2 + b^2)`. The square of the absolute value `|z|^2` is the result of multiplication of `z` by its complex conjugate.\n\nThe sum/difference of two complex numbers involves adding/subtracting their real and imaginary parts separately:\n`(a + i * b) + (c + i * d) = (a + c) + (b + d) * i`,\n`(a + i * b) - (c + i * d) = (a - c) + (b - d) * i`.\n\nMultiplication result is by definition\n`(a + i * b) * (c + i * d) = (a * c - b * d) + (b * c + a * d) * i`.\n\nThe reciprocal of a non-zero complex number is\n`1 / (a + i * b) = a/(a^2 + b^2) - b/(a^2 + b^2) * i`.\n\nDividing a complex number `a + i * b` by another `c + i * d` gives:\n`(a + i * b) / (c + i * d) = (a * c + b * d)/(c^2 + d^2) + (b * c - a * d)/(c^2 + d^2) * i`.\n\nRaising e to a complex exponent can be expressed as `e^(a + i * b) = e^a * e^(i * b)`, the last term of which is given by Euler's formula `e^(i * b) = cos(b) + i * sin(b)`.\n\nImplement the following operations:\n\n- addition, subtraction, multiplication and division of two complex numbers,\n- conjugate, absolute value, exponent of a given complex number.\n\nAssume the programming language you are using does not have an implementation of complex numbers.\n\n\n## C++ interface contract\n\nThe test file is not shown to you, so the interface it expects is stated here in\nfull. Implement exactly these names and signatures; the tests use nothing else.\n\n```cpp\nnamespace complex_numbers {\nclass Complex {\npublic:\n Complex(double real, double imaginary);\n Complex operator+(const Complex& other) const;\n Complex operator-(const Complex& other) const;\n Complex operator*(const Complex& other) const;\n Complex operator/(const Complex& other) const;\n double abs() const;\n Complex conj() const;\n double real() const;\n double imag() const;\n Complex exp() const;\n};\nbool operator==(const Complex& lhs, const Complex& rhs);\nstd::ostream& operator<<(std::ostream& os, Complex const& value);\nComplex operator+(const Complex& complex, double scalar);\nComplex operator+(double scalar, const Complex& complex);\nComplex operator-(const Complex& complex, double scalar);\nComplex operator-(double scalar, const Complex& complex);\nComplex operator*(const Complex& complex, double scalar);\nComplex operator*(double scalar, const Complex& complex);\nComplex operator/(const Complex& complex, double scalar);\nComplex operator/(double scalar, const Complex& complex);\n}\n```\n\nBoth scalar orderings are required for each of the four arithmetic operators. The tests compare with a floating-point tolerance, so exact bit equality is not required.\n\n## Build environment\n\n- The exercise is compiled as C++17 with `-Wall -Wextra -Wpedantic -Werror`, so\n any warning fails the build.\n- Only `complex_numbers.h` and `complex_numbers.cpp` are editable. `CMakeLists.txt` and the test\n file are fixed and must not be modified.\n- The test file includes only `complex_numbers.h`, so every name above must be visible\n from that header.\n- You may either declare in `complex_numbers.h` and define in `complex_numbers.cpp`, or define\n everything `inline`/in-class in `complex_numbers.h` and leave `complex_numbers.cpp` unchanged.\n Both are accepted.\n\n####\n\nUse the above instructions to modify the supplied files: complex_numbers.cpp complex_numbers.h\nDon't change the names of existing functions or classes, as they may be referenced from other code like unit tests, etc.\nOnly use standard libraries, don't suggest installing any packages.\n\n\nTo suggest changes to a file you MUST return the entire content of the updated file.\nYou MUST use this *file listing* format:\n\npath/to/filename.js\n```\n// entire file content ...\n// ... goes in between\n```\n\nEvery *file listing* MUST use this format:\n- First line: the filename with any originally provided path; no extra markup, punctuation, comments, etc. **JUST** the filename with path.\n- Second line: opening ```\n- ... entire content of the file ...\n- Final line: closing ```\n\nTo suggest changes to a file you MUST return a *file listing* that contains the entire content of the file.\n*NEVER* skip, omit or elide content from a *file listing* using \"...\" or by adding comments like \"... rest of code...\"!\nCreate a new file you MUST return a *file listing* which includes an appropriate filename, including any appropriate path.\n\n\n", "role": "user"}], "split": "train", "task_id": "aider-shadow-cpp/complex-numbers"} |
| {"label": "aider-shadow-cpp/crypto-square", "metadata": {"category": "generalized-cpp-global", "data_source": "aider-polyglot-cpp-shadow-grpo", "editable_files": ["crypto_square.cpp", "crypto_square.h"], "episode_kind": "full-solve", "failure_signature": null, "family": "crypto-square", "harness_kind": "shadow_cpp17", "hidden_test_sha256": "3770199d92bda7e4551742ac2d5a30a1970318f18f92f29088f9704a6e67a676", "lineage_id": "polyglot-cpp/crypto-square", "objective_group": "generalized-cpp-global", "problem_id": "crypto-square", "source_prompt_sha256": "1c64e2087dfbcfc0fafe2aa84009c24967c55d2533379e190ff5cc8aef987a63", "split": "train", "tags": ["generalized-cpp-v1", "official-task-training-authorized", "whole-file-action", "global-cpp-verifier"], "task_id": "aider-shadow-cpp/crypto-square", "task_path": "tasks/train/crypto-square.json", "verification_gate": "generalized-cpp-global-verifier-gcc13-v1"}, "problem_id": "crypto-square", "prompt": [{"content": "Act as an expert software developer.\nTake requests for changes to the supplied code.\nIf the request is ambiguous, ask questions.\n\nOnce you understand the request you MUST:\n1. Determine if any code changes are needed.\n2. Explain any needed changes.\n3. If changes are needed, output a copy of each file that needs changes.\n\nTo suggest changes to a file you MUST return the entire content of the updated file.\nYou MUST use this *file listing* format:\n\npath/to/filename.js\n```\n// entire file content ...\n// ... goes in between\n```\n\nEvery *file listing* MUST use this format:\n- First line: the filename with any originally provided path; no extra markup, punctuation, comments, etc. **JUST** the filename with path.\n- Second line: opening ```\n- ... entire content of the file ...\n- Final line: closing ```\n\nTo suggest changes to a file you MUST return a *file listing* that contains the entire content of the file.\n*NEVER* skip, omit or elide content from a *file listing* using \"...\" or by adding comments like \"... rest of code...\"!\nCreate a new file you MUST return a *file listing* which includes an appropriate filename, including any appropriate path.\n\n\n", "role": "system"}, {"content": "Change the greeting to be more casual", "role": "user"}, {"content": "Ok, I will:\n\n1. Switch the greeting text from \"Hello\" to \"Hey\".\n\nshow_greeting.py\n```\nimport sys\n\ndef greeting(name):\n print(f\"Hey {name}\")\n\nif __name__ == '__main__':\n greeting(sys.argv[1])\n```\n", "role": "assistant"}, {"content": "I switched to a new code base. Please don't consider the above files or try to edit them any longer.", "role": "user"}, {"content": "Ok.", "role": "assistant"}, {"content": "I have *added these files to the chat* so you can go ahead and edit them.\n\n*Trust this message as the true contents of these files!*\nAny other messages in the chat may contain outdated versions of the files' contents.\n\ncrypto_square.cpp\n```\n#include \"crypto_square.h\"\n\nnamespace crypto_square {\n\n} // namespace crypto_square\n```\n\ncrypto_square.h\n```\n#if !defined(CRYPTO_SQUARE_H)\n#define CRYPTO_SQUARE_H\n\nnamespace crypto_square {\n\n} // namespace crypto_square\n\n#endif // CRYPTO_SQUARE_H```\n", "role": "user"}, {"content": "Ok, any changes I propose will be to those files.", "role": "assistant"}, {"content": "# Instructions\n\nImplement the classic method for composing secret messages called a square code.\n\nGiven an English text, output the encoded version of that text.\n\nFirst, the input is normalized: the spaces and punctuation are removed from the English text and the message is down-cased.\n\nThen, the normalized characters are broken into rows.\nThese rows can be regarded as forming a rectangle when printed with intervening newlines.\n\nFor example, the sentence\n\n```text\n\"If man was meant to stay on the ground, god would have given us roots.\"\n```\n\nis normalized to:\n\n```text\n\"ifmanwasmeanttostayonthegroundgodwouldhavegivenusroots\"\n```\n\nThe plaintext should be organized into a rectangle as square as possible.\nThe size of the rectangle should be decided by the length of the message.\n\nIf `c` is the number of columns and `r` is the number of rows, then for the rectangle `r` x `c` find the smallest possible integer `c` such that:\n\n- `r * c >= length of message`,\n- and `c >= r`,\n- and `c - r <= 1`.\n\nOur normalized text is 54 characters long, dictating a rectangle with `c = 8` and `r = 7`:\n\n```text\n\"ifmanwas\"\n\"meanttos\"\n\"tayonthe\"\n\"groundgo\"\n\"dwouldha\"\n\"vegivenu\"\n\"sroots \"\n```\n\nThe coded message is obtained by reading down the columns going left to right.\n\nThe message above is coded as:\n\n```text\n\"imtgdvsfearwermayoogoanouuiontnnlvtwttddesaohghnsseoau\"\n```\n\nOutput the encoded text in chunks that fill perfect rectangles `(r X c)`, with `c` chunks of `r` length, separated by spaces.\nFor phrases that are `n` characters short of the perfect rectangle, pad each of the last `n` chunks with a single trailing space.\n\n```text\n\"imtgdvs fearwer mayoogo anouuio ntnnlvt wttddes aohghn sseoau \"\n```\n\nNotice that were we to stack these, we could visually decode the ciphertext back in to the original message:\n\n```text\n\"imtgdvs\"\n\"fearwer\"\n\"mayoogo\"\n\"anouuio\"\n\"ntnnlvt\"\n\"wttddes\"\n\"aohghn \"\n\"sseoau \"\n```\n\n####\n\nUse the above instructions to modify the supplied files: crypto_square.cpp crypto_square.h\nDon't change the names of existing functions or classes, as they may be referenced from other code like unit tests, etc.\nOnly use standard libraries, don't suggest installing any packages.\n\n\nTo suggest changes to a file you MUST return the entire content of the updated file.\nYou MUST use this *file listing* format:\n\npath/to/filename.js\n```\n// entire file content ...\n// ... goes in between\n```\n\nEvery *file listing* MUST use this format:\n- First line: the filename with any originally provided path; no extra markup, punctuation, comments, etc. **JUST** the filename with path.\n- Second line: opening ```\n- ... entire content of the file ...\n- Final line: closing ```\n\nTo suggest changes to a file you MUST return a *file listing* that contains the entire content of the file.\n*NEVER* skip, omit or elide content from a *file listing* using \"...\" or by adding comments like \"... rest of code...\"!\nCreate a new file you MUST return a *file listing* which includes an appropriate filename, including any appropriate path.\n\n\n", "role": "user"}], "split": "train", "task_id": "aider-shadow-cpp/crypto-square"} |
| {"label": "aider-shadow-cpp/grade-school", "metadata": {"category": "generalized-cpp-global", "data_source": "aider-polyglot-cpp-shadow-grpo", "editable_files": ["grade_school.cpp", "grade_school.h"], "episode_kind": "full-solve", "failure_signature": null, "family": "grade-school", "harness_kind": "shadow_cpp17", "hidden_test_sha256": "3a6f4266831b6d31b022e764bed44d1c02cfa10f7629f91053c02e0d53b29871", "lineage_id": "polyglot-cpp/grade-school", "objective_group": "generalized-cpp-global", "problem_id": "grade-school", "source_prompt_sha256": "8dc7133cd5f0564717108757c27ad96ebadf44f03b5fde5c35b826aaeb0b4e0f", "split": "train", "tags": ["generalized-cpp-v1", "official-task-training-authorized", "whole-file-action", "global-cpp-verifier"], "task_id": "aider-shadow-cpp/grade-school", "task_path": "tasks/train/grade-school.json", "verification_gate": "generalized-cpp-global-verifier-gcc13-v1"}, "problem_id": "grade-school", "prompt": [{"content": "Act as an expert software developer.\nTake requests for changes to the supplied code.\nIf the request is ambiguous, ask questions.\n\nOnce you understand the request you MUST:\n1. Determine if any code changes are needed.\n2. Explain any needed changes.\n3. If changes are needed, output a copy of each file that needs changes.\n\nTo suggest changes to a file you MUST return the entire content of the updated file.\nYou MUST use this *file listing* format:\n\npath/to/filename.js\n```\n// entire file content ...\n// ... goes in between\n```\n\nEvery *file listing* MUST use this format:\n- First line: the filename with any originally provided path; no extra markup, punctuation, comments, etc. **JUST** the filename with path.\n- Second line: opening ```\n- ... entire content of the file ...\n- Final line: closing ```\n\nTo suggest changes to a file you MUST return a *file listing* that contains the entire content of the file.\n*NEVER* skip, omit or elide content from a *file listing* using \"...\" or by adding comments like \"... rest of code...\"!\nCreate a new file you MUST return a *file listing* which includes an appropriate filename, including any appropriate path.\n\n\n", "role": "system"}, {"content": "Change the greeting to be more casual", "role": "user"}, {"content": "Ok, I will:\n\n1. Switch the greeting text from \"Hello\" to \"Hey\".\n\nshow_greeting.py\n```\nimport sys\n\ndef greeting(name):\n print(f\"Hey {name}\")\n\nif __name__ == '__main__':\n greeting(sys.argv[1])\n```\n", "role": "assistant"}, {"content": "I switched to a new code base. Please don't consider the above files or try to edit them any longer.", "role": "user"}, {"content": "Ok.", "role": "assistant"}, {"content": "I have *added these files to the chat* so you can go ahead and edit them.\n\n*Trust this message as the true contents of these files!*\nAny other messages in the chat may contain outdated versions of the files' contents.\n\ngrade_school.cpp\n```\n#include \"grade_school.h\"\n\nnamespace grade_school {\n\n} // namespace grade_school\n```\n\ngrade_school.h\n```\n#if !defined(GRADE_SCHOOL_H)\n#define GRADE_SCHOOL_H\n\nnamespace grade_school {\n\n} // namespace grade_school\n\n#endif // GRADE_SCHOOL_H```\n", "role": "user"}, {"content": "Ok, any changes I propose will be to those files.", "role": "assistant"}, {"content": "# Instructions\n\nGiven students' names along with the grade that they are in, create a roster for the school.\n\nIn the end, you should be able to:\n\n- Add a student's name to the roster for a grade\n - \"Add Jim to grade 2.\"\n - \"OK.\"\n- Get a list of all students enrolled in a grade\n - \"Which students are in grade 2?\"\n - \"We've only got Jim just now.\"\n- Get a sorted list of all students in all grades.\n Grades should sort as 1, 2, 3, etc., and students within a grade should be sorted alphabetically by name.\n - \"Who all is enrolled in school right now?\"\n - \"Let me think.\n We have Anna, Barb, and Charlie in grade 1, Alex, Peter, and Zoe in grade 2 and Jim in grade 5.\n So the answer is: Anna, Barb, Charlie, Alex, Peter, Zoe and Jim\"\n\nNote that all our students only have one name (It's a small town, what do you want?) and each student cannot be added more than once to a grade or the roster.\nIn fact, when a test attempts to add the same student more than once, your implementation should indicate that this is incorrect.\n\n####\n\nUse the above instructions to modify the supplied files: grade_school.cpp grade_school.h\nDon't change the names of existing functions or classes, as they may be referenced from other code like unit tests, etc.\nOnly use standard libraries, don't suggest installing any packages.\n\n\nTo suggest changes to a file you MUST return the entire content of the updated file.\nYou MUST use this *file listing* format:\n\npath/to/filename.js\n```\n// entire file content ...\n// ... goes in between\n```\n\nEvery *file listing* MUST use this format:\n- First line: the filename with any originally provided path; no extra markup, punctuation, comments, etc. **JUST** the filename with path.\n- Second line: opening ```\n- ... entire content of the file ...\n- Final line: closing ```\n\nTo suggest changes to a file you MUST return a *file listing* that contains the entire content of the file.\n*NEVER* skip, omit or elide content from a *file listing* using \"...\" or by adding comments like \"... rest of code...\"!\nCreate a new file you MUST return a *file listing* which includes an appropriate filename, including any appropriate path.\n\n\n", "role": "user"}], "split": "train", "task_id": "aider-shadow-cpp/grade-school"} |
| {"label": "aider-shadow-cpp/kindergarten-garden", "metadata": {"category": "generalized-cpp-global", "data_source": "aider-polyglot-cpp-shadow-grpo", "editable_files": ["kindergarten_garden.cpp", "kindergarten_garden.h"], "episode_kind": "full-solve", "failure_signature": null, "family": "kindergarten-garden", "harness_kind": "shadow_cpp17", "hidden_test_sha256": "1a35fe4528cf3577739c95df36daafac894e5e554cf51481ebf8c475f683bcfd", "lineage_id": "polyglot-cpp/kindergarten-garden", "objective_group": "generalized-cpp-global", "problem_id": "kindergarten-garden", "source_prompt_sha256": "0deebfb40706725b72884a95230b3f3a84ed8a16652eb0fdd405ce5516ceacbc", "split": "train", "tags": ["generalized-cpp-v1", "official-task-training-authorized", "whole-file-action", "global-cpp-verifier"], "task_id": "aider-shadow-cpp/kindergarten-garden", "task_path": "tasks/train/kindergarten-garden.json", "verification_gate": "generalized-cpp-global-verifier-gcc13-v1"}, "problem_id": "kindergarten-garden", "prompt": [{"content": "Act as an expert software developer.\nTake requests for changes to the supplied code.\nIf the request is ambiguous, ask questions.\n\nOnce you understand the request you MUST:\n1. Determine if any code changes are needed.\n2. Explain any needed changes.\n3. If changes are needed, output a copy of each file that needs changes.\n\nTo suggest changes to a file you MUST return the entire content of the updated file.\nYou MUST use this *file listing* format:\n\npath/to/filename.js\n```\n// entire file content ...\n// ... goes in between\n```\n\nEvery *file listing* MUST use this format:\n- First line: the filename with any originally provided path; no extra markup, punctuation, comments, etc. **JUST** the filename with path.\n- Second line: opening ```\n- ... entire content of the file ...\n- Final line: closing ```\n\nTo suggest changes to a file you MUST return a *file listing* that contains the entire content of the file.\n*NEVER* skip, omit or elide content from a *file listing* using \"...\" or by adding comments like \"... rest of code...\"!\nCreate a new file you MUST return a *file listing* which includes an appropriate filename, including any appropriate path.\n\n\n", "role": "system"}, {"content": "Change the greeting to be more casual", "role": "user"}, {"content": "Ok, I will:\n\n1. Switch the greeting text from \"Hello\" to \"Hey\".\n\nshow_greeting.py\n```\nimport sys\n\ndef greeting(name):\n print(f\"Hey {name}\")\n\nif __name__ == '__main__':\n greeting(sys.argv[1])\n```\n", "role": "assistant"}, {"content": "I switched to a new code base. Please don't consider the above files or try to edit them any longer.", "role": "user"}, {"content": "Ok.", "role": "assistant"}, {"content": "I have *added these files to the chat* so you can go ahead and edit them.\n\n*Trust this message as the true contents of these files!*\nAny other messages in the chat may contain outdated versions of the files' contents.\n\nkindergarten_garden.cpp\n```\n#include \"kindergarten_garden.h\"\n\nnamespace kindergarten_garden {\n\n} // namespace kindergarten_garden\n```\n\nkindergarten_garden.h\n```\n#pragma once\n\nnamespace kindergarten_garden {\n\n} // namespace kindergarten_garden\n```\n", "role": "user"}, {"content": "Ok, any changes I propose will be to those files.", "role": "assistant"}, {"content": "# Instructions\n\nYour task is to, given a diagram, determine which plants each child in the kindergarten class is responsible for.\n\nThere are 12 children in the class:\n\n- Alice, Bob, Charlie, David, Eve, Fred, Ginny, Harriet, Ileana, Joseph, Kincaid, and Larry.\n\nFour different types of seeds are planted:\n\n| Plant | Diagram encoding |\n| ------ | ---------------- |\n| Grass | G |\n| Clover | C |\n| Radish | R |\n| Violet | V |\n\nEach child gets four cups, two on each row:\n\n```text\n[window][window][window]\n........................ # each dot represents a cup\n........................\n```\n\nTheir teacher assigns cups to the children alphabetically by their names, which means that Alice comes first and Larry comes last.\n\nHere is an example diagram representing Alice's plants:\n\n```text\n[window][window][window]\nVR......................\nRG......................\n```\n\nIn the first row, nearest the windows, she has a violet and a radish.\nIn the second row she has a radish and some grass.\n\nYour program will be given the plants from left-to-right starting with the row nearest the windows.\nFrom this, it should be able to determine which plants belong to each student.\n\nFor example, if it's told that the garden looks like so:\n\n```text\n[window][window][window]\nVRCGVVRVCGGCCGVRGCVCGCGV\nVRCCCGCRRGVCGCRVVCVGCGCV\n```\n\nThen if asked for Alice's plants, it should provide:\n\n- Violets, radishes, violets, radishes\n\nWhile asking for Bob's plants would yield:\n\n- Clover, grass, clover, clover\n\n####\n\nUse the above instructions to modify the supplied files: kindergarten_garden.cpp kindergarten_garden.h\nDon't change the names of existing functions or classes, as they may be referenced from other code like unit tests, etc.\nOnly use standard libraries, don't suggest installing any packages.\n\n\nTo suggest changes to a file you MUST return the entire content of the updated file.\nYou MUST use this *file listing* format:\n\npath/to/filename.js\n```\n// entire file content ...\n// ... goes in between\n```\n\nEvery *file listing* MUST use this format:\n- First line: the filename with any originally provided path; no extra markup, punctuation, comments, etc. **JUST** the filename with path.\n- Second line: opening ```\n- ... entire content of the file ...\n- Final line: closing ```\n\nTo suggest changes to a file you MUST return a *file listing* that contains the entire content of the file.\n*NEVER* skip, omit or elide content from a *file listing* using \"...\" or by adding comments like \"... rest of code...\"!\nCreate a new file you MUST return a *file listing* which includes an appropriate filename, including any appropriate path.\n\n\n", "role": "user"}], "split": "train", "task_id": "aider-shadow-cpp/kindergarten-garden"} |
| {"label": "aider-shadow-cpp/perfect-numbers", "metadata": {"category": "generalized-cpp-global", "data_source": "aider-polyglot-cpp-shadow-grpo", "editable_files": ["perfect_numbers.cpp", "perfect_numbers.h"], "episode_kind": "full-solve", "failure_signature": null, "family": "perfect-numbers", "harness_kind": "shadow_cpp17", "hidden_test_sha256": "fa206f8feaa1f8aa63986db34fc96458b30ab0325c0855fd6659ab7cbcb50be3", "lineage_id": "polyglot-cpp/perfect-numbers", "objective_group": "generalized-cpp-global", "problem_id": "perfect-numbers", "source_prompt_sha256": "8db797c5f8e9c0efbb8c805ddefca892f764b4f3a72dff65c037f4bffb92b1cb", "split": "train", "tags": ["generalized-cpp-v1", "official-task-training-authorized", "whole-file-action", "global-cpp-verifier"], "task_id": "aider-shadow-cpp/perfect-numbers", "task_path": "tasks/train/perfect-numbers.json", "verification_gate": "generalized-cpp-global-verifier-gcc13-v1"}, "problem_id": "perfect-numbers", "prompt": [{"content": "Act as an expert software developer.\nTake requests for changes to the supplied code.\nIf the request is ambiguous, ask questions.\n\nOnce you understand the request you MUST:\n1. Determine if any code changes are needed.\n2. Explain any needed changes.\n3. If changes are needed, output a copy of each file that needs changes.\n\nTo suggest changes to a file you MUST return the entire content of the updated file.\nYou MUST use this *file listing* format:\n\npath/to/filename.js\n```\n// entire file content ...\n// ... goes in between\n```\n\nEvery *file listing* MUST use this format:\n- First line: the filename with any originally provided path; no extra markup, punctuation, comments, etc. **JUST** the filename with path.\n- Second line: opening ```\n- ... entire content of the file ...\n- Final line: closing ```\n\nTo suggest changes to a file you MUST return a *file listing* that contains the entire content of the file.\n*NEVER* skip, omit or elide content from a *file listing* using \"...\" or by adding comments like \"... rest of code...\"!\nCreate a new file you MUST return a *file listing* which includes an appropriate filename, including any appropriate path.\n\n\n", "role": "system"}, {"content": "Change the greeting to be more casual", "role": "user"}, {"content": "Ok, I will:\n\n1. Switch the greeting text from \"Hello\" to \"Hey\".\n\nshow_greeting.py\n```\nimport sys\n\ndef greeting(name):\n print(f\"Hey {name}\")\n\nif __name__ == '__main__':\n greeting(sys.argv[1])\n```\n", "role": "assistant"}, {"content": "I switched to a new code base. Please don't consider the above files or try to edit them any longer.", "role": "user"}, {"content": "Ok.", "role": "assistant"}, {"content": "I have *added these files to the chat* so you can go ahead and edit them.\n\n*Trust this message as the true contents of these files!*\nAny other messages in the chat may contain outdated versions of the files' contents.\n\nperfect_numbers.cpp\n```\n#include \"perfect_numbers.h\"\n\nnamespace perfect_numbers {} // namespace perfect_numbers\n```\n\nperfect_numbers.h\n```\n#if !defined(PERFECT_NUMBERS_H)\n#define PERFECT_NUMBERS_H\n\nnamespace perfect_numbers {} // namespace perfect_numbers\n\n#endif // PERFECT_NUMBERS_H```\n", "role": "user"}, {"content": "Ok, any changes I propose will be to those files.", "role": "assistant"}, {"content": "# Instructions\n\nDetermine if a number is perfect, abundant, or deficient based on Nicomachus' (60 - 120 CE) classification scheme for positive integers.\n\nThe Greek mathematician [Nicomachus][nicomachus] devised a classification scheme for positive integers, identifying each as belonging uniquely to the categories of [perfect](#perfect), [abundant](#abundant), or [deficient](#deficient) based on their [aliquot sum][aliquot-sum].\nThe _aliquot sum_ is defined as the sum of the factors of a number not including the number itself.\nFor example, the aliquot sum of `15` is `1 + 3 + 5 = 9`.\n\n## Perfect\n\nA number is perfect when it equals its aliquot sum.\nFor example:\n\n- `6` is a perfect number because `1 + 2 + 3 = 6`\n- `28` is a perfect number because `1 + 2 + 4 + 7 + 14 = 28`\n\n## Abundant\n\nA number is abundant when it is less than its aliquot sum.\nFor example:\n\n- `12` is an abundant number because `1 + 2 + 3 + 4 + 6 = 16`\n- `24` is an abundant number because `1 + 2 + 3 + 4 + 6 + 8 + 12 = 36`\n\n## Deficient\n\nA number is deficient when it is greater than its aliquot sum.\nFor example:\n\n- `8` is a deficient number because `1 + 2 + 4 = 7`\n- Prime numbers are deficient\n\n## Task\n\nImplement a way to determine whether a given number is [perfect](#perfect).\nDepending on your language track, you may also need to implement a way to determine whether a given number is [abundant](#abundant) or [deficient](#deficient).\n\n[nicomachus]: https://en.wikipedia.org/wiki/Nicomachus\n[aliquot-sum]: https://en.wikipedia.org/wiki/Aliquot_sum\n\n####\n\nUse the above instructions to modify the supplied files: perfect_numbers.cpp perfect_numbers.h\nDon't change the names of existing functions or classes, as they may be referenced from other code like unit tests, etc.\nOnly use standard libraries, don't suggest installing any packages.\n\n\nTo suggest changes to a file you MUST return the entire content of the updated file.\nYou MUST use this *file listing* format:\n\npath/to/filename.js\n```\n// entire file content ...\n// ... goes in between\n```\n\nEvery *file listing* MUST use this format:\n- First line: the filename with any originally provided path; no extra markup, punctuation, comments, etc. **JUST** the filename with path.\n- Second line: opening ```\n- ... entire content of the file ...\n- Final line: closing ```\n\nTo suggest changes to a file you MUST return a *file listing* that contains the entire content of the file.\n*NEVER* skip, omit or elide content from a *file listing* using \"...\" or by adding comments like \"... rest of code...\"!\nCreate a new file you MUST return a *file listing* which includes an appropriate filename, including any appropriate path.\n\n\n", "role": "user"}], "split": "train", "task_id": "aider-shadow-cpp/perfect-numbers"} |
|
|
