|
| 1 | +--- |
| 2 | +title: "Translating C To Rust: Lessons from a User Study" |
| 3 | + |
| 4 | +event: Weekly Talk |
| 5 | +event_url: |
| 6 | + |
| 7 | +location: COM3-B1-15 - Meeting Rm 92 |
| 8 | +address: |
| 9 | + street: |
| 10 | + city: |
| 11 | + region: |
| 12 | + postcode: |
| 13 | + country: Singapore |
| 14 | + |
| 15 | +summary: |
| 16 | +abstract: "Rust aims to offer full memory safety for programs, a guarantee that untamed C programs do not enjoy. How difficult is it to translate existing C code to Rust? To get a complementary view from that of automatic C to Rust translators, we report on a user study asking humans to translate real-world C programs to Rust. Our participants are able to produce safe Rust translations, whereas state-of-the-art automatic tools are not able to do so. Our analysis highlights that the high-level strategy taken by users departs significantly from those of automatic tools we study. We also find that users often choose zero-cost (static) abstractions for temporal safety, which addresses a predominant component of runtime costs in other full memory safety defenses. User-provided translations showcase a rich landscape of specialized strategies to translate the same C program in different ways to safe Rust, which future automatic translators can consider." |
| 17 | + |
| 18 | +# Talk start and end times. |
| 19 | +# End time can optionally be hidden by prefixing the line with `#`. |
| 20 | +date: "2025-03-11T14:00:00Z" |
| 21 | +date_end: "2025-03-11T15:00:00Z" |
| 22 | +all_day: false |
| 23 | + |
| 24 | +# Schedule page publish date (NOT talk date). |
| 25 | +publishDate: "2017-01-01T00:00:00Z" |
| 26 | + |
| 27 | +authors: [Ruishi Li] |
| 28 | +tags: [Weekly Talk] |
| 29 | + |
| 30 | +# Is this a featured talk? (true/false) |
| 31 | +featured: false |
| 32 | + |
| 33 | +image: |
| 34 | + caption: 'Image credit: [**Unsplash**](https://unsplash.com/photos/bzdhc5b3Bxs)' |
| 35 | + focal_point: Right |
| 36 | + |
| 37 | +url_code: "" |
| 38 | +url_pdf: "" |
| 39 | +url_slides: "" |
| 40 | +url_video: "" |
| 41 | + |
| 42 | +# Markdown Slides (optional). |
| 43 | +# Associate this talk with Markdown slides. |
| 44 | +# Simply enter your slide deck's filename without extension. |
| 45 | +# E.g. `slides = "example-slides"` references `content/slides/example-slides.md`. |
| 46 | +# Otherwise, set `slides = ""`. |
| 47 | +slides: |
| 48 | + |
| 49 | +# Projects (optional). |
| 50 | +# Associate this post with one or more of your projects. |
| 51 | +# Simply enter your project's folder or file name without extension. |
| 52 | +# E.g. `projects = ["internal-project"]` references `content/project/deep-learning/index.md`. |
| 53 | +# Otherwise, set `projects = []`. |
| 54 | +projects: |
| 55 | + |
| 56 | +# Slides can be added in a few ways: |
| 57 | +# |
| 58 | +# - **Create** slides using Wowchemy's [*Slides*](https://wowchemy.com/docs/managing-content/#create-slides) feature and link using `slides` parameter in the front matter of the talk file |
| 59 | +# - **Upload** an existing slide deck to `static/` and link using `url_slides` parameter in the front matter of the talk file |
| 60 | +# - **Embed** your slides (e.g. Google Slides) or presentation video on this page using [shortcodes](https://wowchemy.com/docs/writing-markdown-latex/). |
| 61 | +# |
| 62 | +# Further event details, including page elements such as image galleries, can be added to the body of this page. |
| 63 | + |
| 64 | + |
| 65 | +--- |
0 commit comments