REVIEW 2 cited by
Unsupervised Evaluation of Code LLMs with Round-Trip Correctness
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
To evaluate code large language models (LLMs), research has relied on a few small manually curated benchmarks, such as HumanEval and MBPP, which represent a narrow part of the real-world software domains. In this work, we introduce round-trip correctness (RTC) as an alternative evaluation method. RTC allows Code LLM evaluation on a broader spectrum of real-world software domains without the need for costly human curation. RTC rests on the idea that we can ask a model to make a prediction (e.g., describe some code using natural language), feed that prediction back (e.g., synthesize code from the predicted description), and check if this round-trip leads to code that is semantically equivalent to the original input. We show how to employ RTC to evaluate code synthesis and editing. We find that RTC strongly correlates with model performance on existing narrow-domain code synthesis benchmarks while allowing us to expand to a much broader set of domains and tasks which was not previously possible without costly human annotations.
Forward citations
Cited by 2 Pith papers
-
Round-Trip Mutation Testing: Translating Code to Natural Language Intent and back
LLM code↔intent round-trips yield diverse mutants that, at a 4-test budget, detect about four times more real BugsInPy faults than traditional mutation operators.
-
AI4Contracts: LLM & RAG-Powered Encoding of Financial Derivative Contracts
CDMizer uses example-derived templates, depth-based retrieval, and hierarchical LLM generation to convert OTC derivative contract text into CDM JSON, achieving guaranteed schema adherence and improved semantic coverag...
Discussion (0). Continue with ORCID to comment.