Adds Specification Formatting for 2011 Finding Maximum in An Array - #1
Open
LudwigVonChesterfield wants to merge 1 commit into
Open
LudwigVonChesterfield wants to merge 1 commit into
LudwigVonChesterfield wants to merge 1 commit into
Conversation
…m in an Array problem
| //enddatastructures | ||
|
|
||
| //preconditions | ||
| // Encodes: A non-empty integer array a. |
There was a problem hiding this comment.
Should we have descriptions like these to show which preconditions link to what parts of the natural-language problem (or an assumption we infer is necessary to the solution)?
There was a problem hiding this comment.
Good Point! We should allow one line docstring to explain the assumption.
|
Yep that field is for more complex ds and for completeness. I also suggest to put in input parameters and output return value. Pls see the new template (and add the encodes field you suggested!) We will give model the template, and ask it to return output in this format. 99% of the time it should. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TBD if this is the format we'll go with.
I'm unsure of the use of //datastructures section, is it for Tree-like problems (or other problems with non-primitive types?)
I'm also wondering how we'll use this formatting to ensure that LLM-generated output is compatible with the ground truth. Would we modify the prompts of the challenges and re-train models, or would we have a separate process to make emitted code compatible with these specs?