Browse State-of-the-Art › Code Comment Generation

Code Comment Generation

4 papers with code · 1 benchmark · 2 datasets archive 2025-07-28

Computer Code

Benchmarks archive 2025-07-28

1 leaderboard table shown for this task, 1 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted.

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
DeepCom (1 row) CodeTrans-TF-Large CodeTrans: Towards Cracking the Language of Silicon's Code Through... code — Compare

Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

Libraries

Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.

Datasets archive 2025-07-28

2 datasets whose archive record lists this task, ordered by the archive's paper count.

Subtasks archive 2025-07-28

No subtask under this task in the archive's task tree.

Papers archive 2025-07-28

archive papers tagged: 10 · with a code link: 4 · where Syntology ran a sample: 0 (0 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran: none of the 10 tagged papers has a Syntology run on record

Page 1 of 1: papers 1 to 10 of 10, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.

Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from.

  • 29 May 2022 2 repositories listed
    We validate CoNT on five generation tasks with ten benchmarks, including machine translation, summarization, code comment generation, data-to-text generation and commonsense generation.
  • 24 Jan 2024 1 repository listed
    GPT-based models are one of the popular ones studied for tasks such as code comment generation or test generation.
  • 6 Apr 2021 1 repository listed
    Simultaneously, the transformer model, especially its combination with transfer learning, has been proven to be a powerful technique for natural language processing tasks.
  • 9 Oct 2020 1 repository listed
    Inspired by the IR-based and template-based approaches, in this paper, we propose a neural comment generation approach where we use the existing comments of similar code snippets as exemplars to guide comment generation.
  • APIContext2Com: Code Comment Generation by Incorporating Pre-Defined API Documentation
    3 Mar 2023 0 repositories listed
    Code comments are significantly helpful in comprehending software programs and also aid developers to save a great deal of time in software maintenance.
  • LAMNER: Code Comment Generation Using Character Language Model and Named Entity Recognition
    5 Apr 2022 0 repositories listed
    Code comment generation is the task of generating a high-level natural language description for a given code method or function.
  • InferCode: Self-Supervised Learning of Code Representations by Predicting Subtrees
    13 Dec 2020 0 repositories listed
    Building deep learning models on source code has found many successful software engineering applications, such as code search, code comment generation, bug detection, code migration, and so on.
  • Learning to Represent Programs with Heterogeneous Graphs
    8 Dec 2020 0 repositories listed
    Program source code contains complex structure information, which can be represented in structured data forms like trees or graphs.
  • Towards Context-Aware Code Comment Generation
    1 Nov 2020 0 repositories listed
    Code comments are vital for software maintenance and comprehension, but many software projects suffer from the lack of meaningful and up-to-date comments in practice.
  • TAG : Type Auxiliary Guiding for Code Comment Generation
    6 May 2020 0 repositories listed
    Existing leading code comment generation approaches with the structure-to-sequence framework ignores the type information of the interpretation of the code, e.g., operator, string, etc.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections