<?xml version='1.0' encoding='UTF-8'?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-04-19T17:07:47Z</responseDate>
  <request verb="GetRecord" metadataPrefix="oai_dc" identifier="oai:ipsj.ixsq.nii.ac.jp:00219052">https://ipsj.ixsq.nii.ac.jp/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:ipsj.ixsq.nii.ac.jp:00219052</identifier>
        <datestamp>2025-01-19T14:56:32Z</datestamp>
        <setSpec>1164:1384:10896:10984</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns="http://www.w3.org/2001/XMLSchema" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>Code Clone Detection in Rust Intermediate Representation</dc:title>
          <dc:title>Code Clone Detection in Rust Intermediate Representation</dc:title>
          <dc:creator>Davide, Pizzolotto</dc:creator>
          <dc:creator>Makoto, Matsushita</dc:creator>
          <dc:creator>Katsuro, Inoue</dc:creator>
          <dc:creator>Davide, Pizzolotto</dc:creator>
          <dc:creator>Makoto, Matsushita</dc:creator>
          <dc:creator>Katsuro, Inoue</dc:creator>
          <dc:description>Code reuse is a common practice while developing software. While the detection of identical and nearly identical portions of code reached high accuracy, in the past years efforts shifted toward detecting seemingly different clones but with the same semantic value, anlysing almost always the Java language only. In newer languages, however, analysis is often complicated by the presence of syntactic sugar. In this paper we present an analysis of clones in the Rust language ecosystem at different compilation steps. The various stages in the Rust compilation, progressively flatten the code and remove unnecessary decorations until binary representation is reached. We analysed several Rust projects at source level and High-level IR, and compared the amount and types of clones for each refinement level.</dc:description>
          <dc:description>Code reuse is a common practice while developing software. While the detection of identical and nearly identical portions of code reached high accuracy, in the past years efforts shifted toward detecting seemingly different clones but with the same semantic value, anlysing almost always the Java language only. In newer languages, however, analysis is often complicated by the presence of syntactic sugar. In this paper we present an analysis of clones in the Rust language ecosystem at different compilation steps. The various stages in the Rust compilation, progressively flatten the code and remove unnecessary decorations until binary representation is reached. We analysed several Rust projects at source level and High-level IR, and compared the amount and types of clones for each refinement level.</dc:description>
          <dc:description>technical report</dc:description>
          <dc:publisher>情報処理学会</dc:publisher>
          <dc:date>2022-07-21</dc:date>
          <dc:format>application/pdf</dc:format>
          <dc:identifier>研究報告ソフトウェア工学（SE）</dc:identifier>
          <dc:identifier>26</dc:identifier>
          <dc:identifier>2022-SE-211</dc:identifier>
          <dc:identifier>1</dc:identifier>
          <dc:identifier>7</dc:identifier>
          <dc:identifier>2188-8825</dc:identifier>
          <dc:identifier>AN10112981</dc:identifier>
          <dc:identifier>https://ipsj.ixsq.nii.ac.jp/record/219052/files/IPSJ-SE22211026.pdf</dc:identifier>
          <dc:language>eng</dc:language>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
