Replacements and Replaceables: Making the Case for Code Variants
There are often multiple ways to implement the same requirement in source code. Different implementation choices can result in code snippets that are similar, and have been defined in multiple ways: code clones, examples, simions and variants. Currently, there is a lack of a consistent and unambiguo...
Gespeichert in:
Veröffentlicht in: | arXiv.org 2020-06 |
---|---|
Hauptverfasser: | , , , , |
Format: | Artikel |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
container_end_page | |
---|---|
container_issue | |
container_start_page | |
container_title | arXiv.org |
container_volume | |
creator | Vinayakarao, Venkatesh Sondhi, Devika Keswani, Sumit Purandare, Rahul Sarma, Anita |
description | There are often multiple ways to implement the same requirement in source code. Different implementation choices can result in code snippets that are similar, and have been defined in multiple ways: code clones, examples, simions and variants. Currently, there is a lack of a consistent and unambiguous definition of such types of code snippets. Here we present a characterization study of code variants - a specific type of code snippets that differ from each other by at least one desired property, within a given code context. We distinguish code variants from other types of redundancies in source code, and demonstrate the significant role that they play: about 25% to 43% of developer discussions (in a set of nine open source projects) were about variants. We characterize different types of variants based on their code context and desired properties. As a demonstration of the possible use of our characterization of code variants, we show how search results can be ranked based on a desired property (e.g., speed of execution). |
format | Article |
fullrecord | <record><control><sourceid>proquest</sourceid><recordid>TN_cdi_proquest_journals_2410890104</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>2410890104</sourcerecordid><originalsourceid>FETCH-proquest_journals_24108901043</originalsourceid><addsrcrecordid>eNpjYuA0MjY21LUwMTLiYOAtLs4yMDAwMjM3MjU15mRwCEotyElMTs1NzSspVkjMS1GACiQm5aQWWyn4JmZn5qUrlGSkKjgnFqcqpOUXKTjnp6QqhCUWZSYC9fAwsKYl5hSn8kJpbgZlN9cQZw_dgqL8wtLU4pL4rPzSojygVLyRiaGBhaWBoYGJMXGqAOElODA</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>2410890104</pqid></control><display><type>article</type><title>Replacements and Replaceables: Making the Case for Code Variants</title><source>Free E- Journals</source><creator>Vinayakarao, Venkatesh ; Sondhi, Devika ; Keswani, Sumit ; Purandare, Rahul ; Sarma, Anita</creator><creatorcontrib>Vinayakarao, Venkatesh ; Sondhi, Devika ; Keswani, Sumit ; Purandare, Rahul ; Sarma, Anita</creatorcontrib><description>There are often multiple ways to implement the same requirement in source code. Different implementation choices can result in code snippets that are similar, and have been defined in multiple ways: code clones, examples, simions and variants. Currently, there is a lack of a consistent and unambiguous definition of such types of code snippets. Here we present a characterization study of code variants - a specific type of code snippets that differ from each other by at least one desired property, within a given code context. We distinguish code variants from other types of redundancies in source code, and demonstrate the significant role that they play: about 25% to 43% of developer discussions (in a set of nine open source projects) were about variants. We characterize different types of variants based on their code context and desired properties. As a demonstration of the possible use of our characterization of code variants, we show how search results can be ranked based on a desired property (e.g., speed of execution).</description><identifier>EISSN: 2331-8422</identifier><language>eng</language><publisher>Ithaca: Cornell University Library, arXiv.org</publisher><subject>Context ; Source code</subject><ispartof>arXiv.org, 2020-06</ispartof><rights>2020. This work is published under http://arxiv.org/licenses/nonexclusive-distrib/1.0/ (the “License”). Notwithstanding the ProQuest Terms and Conditions, you may use this content in accordance with the terms of the License.</rights><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><link.rule.ids>776,780</link.rule.ids></links><search><creatorcontrib>Vinayakarao, Venkatesh</creatorcontrib><creatorcontrib>Sondhi, Devika</creatorcontrib><creatorcontrib>Keswani, Sumit</creatorcontrib><creatorcontrib>Purandare, Rahul</creatorcontrib><creatorcontrib>Sarma, Anita</creatorcontrib><title>Replacements and Replaceables: Making the Case for Code Variants</title><title>arXiv.org</title><description>There are often multiple ways to implement the same requirement in source code. Different implementation choices can result in code snippets that are similar, and have been defined in multiple ways: code clones, examples, simions and variants. Currently, there is a lack of a consistent and unambiguous definition of such types of code snippets. Here we present a characterization study of code variants - a specific type of code snippets that differ from each other by at least one desired property, within a given code context. We distinguish code variants from other types of redundancies in source code, and demonstrate the significant role that they play: about 25% to 43% of developer discussions (in a set of nine open source projects) were about variants. We characterize different types of variants based on their code context and desired properties. As a demonstration of the possible use of our characterization of code variants, we show how search results can be ranked based on a desired property (e.g., speed of execution).</description><subject>Context</subject><subject>Source code</subject><issn>2331-8422</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2020</creationdate><recordtype>article</recordtype><sourceid>BENPR</sourceid><recordid>eNpjYuA0MjY21LUwMTLiYOAtLs4yMDAwMjM3MjU15mRwCEotyElMTs1NzSspVkjMS1GACiQm5aQWWyn4JmZn5qUrlGSkKjgnFqcqpOUXKTjnp6QqhCUWZSYC9fAwsKYl5hSn8kJpbgZlN9cQZw_dgqL8wtLU4pL4rPzSojygVLyRiaGBhaWBoYGJMXGqAOElODA</recordid><startdate>20200614</startdate><enddate>20200614</enddate><creator>Vinayakarao, Venkatesh</creator><creator>Sondhi, Devika</creator><creator>Keswani, Sumit</creator><creator>Purandare, Rahul</creator><creator>Sarma, Anita</creator><general>Cornell University Library, arXiv.org</general><scope>8FE</scope><scope>8FG</scope><scope>ABJCF</scope><scope>ABUWG</scope><scope>AFKRA</scope><scope>AZQEC</scope><scope>BENPR</scope><scope>BGLVJ</scope><scope>CCPQU</scope><scope>DWQXO</scope><scope>HCIFZ</scope><scope>L6V</scope><scope>M7S</scope><scope>PIMPY</scope><scope>PQEST</scope><scope>PQQKQ</scope><scope>PQUKI</scope><scope>PRINS</scope><scope>PTHSS</scope></search><sort><creationdate>20200614</creationdate><title>Replacements and Replaceables: Making the Case for Code Variants</title><author>Vinayakarao, Venkatesh ; Sondhi, Devika ; Keswani, Sumit ; Purandare, Rahul ; Sarma, Anita</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-proquest_journals_24108901043</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2020</creationdate><topic>Context</topic><topic>Source code</topic><toplevel>online_resources</toplevel><creatorcontrib>Vinayakarao, Venkatesh</creatorcontrib><creatorcontrib>Sondhi, Devika</creatorcontrib><creatorcontrib>Keswani, Sumit</creatorcontrib><creatorcontrib>Purandare, Rahul</creatorcontrib><creatorcontrib>Sarma, Anita</creatorcontrib><collection>ProQuest SciTech Collection</collection><collection>ProQuest Technology Collection</collection><collection>Materials Science & Engineering Collection</collection><collection>ProQuest Central (Alumni Edition)</collection><collection>ProQuest Central UK/Ireland</collection><collection>ProQuest Central Essentials</collection><collection>ProQuest Central</collection><collection>Technology Collection</collection><collection>ProQuest One Community College</collection><collection>ProQuest Central Korea</collection><collection>SciTech Premium Collection</collection><collection>ProQuest Engineering Collection</collection><collection>Engineering Database</collection><collection>Publicly Available Content Database</collection><collection>ProQuest One Academic Eastern Edition (DO NOT USE)</collection><collection>ProQuest One Academic</collection><collection>ProQuest One Academic UKI Edition</collection><collection>ProQuest Central China</collection><collection>Engineering Collection</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Vinayakarao, Venkatesh</au><au>Sondhi, Devika</au><au>Keswani, Sumit</au><au>Purandare, Rahul</au><au>Sarma, Anita</au><format>book</format><genre>document</genre><ristype>GEN</ristype><atitle>Replacements and Replaceables: Making the Case for Code Variants</atitle><jtitle>arXiv.org</jtitle><date>2020-06-14</date><risdate>2020</risdate><eissn>2331-8422</eissn><abstract>There are often multiple ways to implement the same requirement in source code. Different implementation choices can result in code snippets that are similar, and have been defined in multiple ways: code clones, examples, simions and variants. Currently, there is a lack of a consistent and unambiguous definition of such types of code snippets. Here we present a characterization study of code variants - a specific type of code snippets that differ from each other by at least one desired property, within a given code context. We distinguish code variants from other types of redundancies in source code, and demonstrate the significant role that they play: about 25% to 43% of developer discussions (in a set of nine open source projects) were about variants. We characterize different types of variants based on their code context and desired properties. As a demonstration of the possible use of our characterization of code variants, we show how search results can be ranked based on a desired property (e.g., speed of execution).</abstract><cop>Ithaca</cop><pub>Cornell University Library, arXiv.org</pub><oa>free_for_read</oa></addata></record> |
fulltext | fulltext |
identifier | EISSN: 2331-8422 |
ispartof | arXiv.org, 2020-06 |
issn | 2331-8422 |
language | eng |
recordid | cdi_proquest_journals_2410890104 |
source | Free E- Journals |
subjects | Context Source code |
title | Replacements and Replaceables: Making the Case for Code Variants |
url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-02-08T21%3A30%3A49IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest&rft_val_fmt=info:ofi/fmt:kev:mtx:book&rft.genre=document&rft.atitle=Replacements%20and%20Replaceables:%20Making%20the%20Case%20for%20Code%20Variants&rft.jtitle=arXiv.org&rft.au=Vinayakarao,%20Venkatesh&rft.date=2020-06-14&rft.eissn=2331-8422&rft_id=info:doi/&rft_dat=%3Cproquest%3E2410890104%3C/proquest%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=2410890104&rft_id=info:pmid/&rfr_iscdi=true |