Cited by 155Software Engineering ResearchSoftware Engineering Techniques and PracticesSoftware Testing and Debugging Techniques

How Program History Can Improve Code Completion

Robbes, Romain, Lanza, Michele·2008·2008 23rd IEEE/ACM International Conference on Automated Software Engineering

Abstract

Code completion is a widely used productivity tool. It takes away the burden of remembering and typing the exact names of methods or classes: As a developer starts typing a name, it provides a progressively refined list of candidates matching the name. However, the candidate list always comes in alphabetic order, i.e., the environment is only second-guessing the name based on pattern matching. Finding the correct candidate can be cumbersome or slower than typing the full name. We present an approach to improve code completion with program history. We define a benchmark measuring the accuracy and usefulness of a code completion engine. Further, we use the change history data to also improve the results offered by code completion tools. Finally, we propose an alternative interface for completion tools.

Integrity signals

Registry

Crossref · 10.1109/ase.2008.42

Cites

9 of 9 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

We couldn’t retrieve this paper’s full text, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • In Py150-wilds, the task focuses on class name and method name prediction because developer studies indicate these are used most commonly by developers.

    “To define a task closer to real applications, in Py150-wilds we focus on class name and method name prediction (which are used most commonly by developers).”

    From WILDS: A Benchmark of in-the-Wild Distribution Shifts (2020) · cites this paper as Robbes and Lanza, 2008

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Robbes, R., & Lanza, M.
Affiliations
Università della Svizzera italiana (CH)
Venue
2008 23rd IEEE/ACM International Conference on Automated Software Engineering
Publisher
IEEE
Published
2008-09
Pages
317-326
OpenAlex
W2166597811
Cited by
155
References
9
Citations by year
2026: 2 · 2025: 8 · 2024: 11 · 2023: 9 · 2022: 6 · 2021: 7 · 2020: 12 · 2019: 11 · 2018: 4 · 2017: 7 · 2016: 9 · 2015: 10 · 2014: 14 · 2013: 6 · 2012: 14
FWCI
6.55
Type
conference paper
Language
en
Open access
closed
Locations
  • IEEE/ACM International Conference on Automated Software Engineering (ASE) (publishedVersion)
  • Open Research (University of Surrey) (submittedVersion)
Funders
  • National Science Foundation
  • Schweizerischer Nationalfonds zur Förderung der Wissenschaftlichen Forschung (115990)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
Keywords
code completion, program history, change history, developer productivity

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review