X-Git-Url: https://git.ralfj.de/web.git/blobdiff_plain/b84528e59995968211680b1aa38d046dc81531a6..a448e297bd91c98e949afcef1cd63855be7a2375:/personal/_posts/2018-07-11-research-assistant.md diff --git a/personal/_posts/2018-07-11-research-assistant.md b/personal/_posts/2018-07-11-research-assistant.md index 7ff0d91..0641bef 100644 --- a/personal/_posts/2018-07-11-research-assistant.md +++ b/personal/_posts/2018-07-11-research-assistant.md @@ -3,16 +3,16 @@ title: "Back at Mozilla" categories: internship rust --- -After my [internship last year has ended]({{ site.baseurl }}{% post_url 2017-08-12-internship-ending %}), I naturally became somewhat less active in the Rust community as I could not work on Rust full-time any more. +After my [internship last year has ended]({% post_url 2017-08-12-internship-ending %}), I naturally became somewhat less active in the Rust community as I could not work on Rust full-time any more. Well, for the following months I am going to be back full-time. :) Thanks to @aturon, I am able to work as a research assistant for Mozilla during this summer (until the end of November). I don't really know what a "research assistant" is, but I am going to continue the work on Rust memory models, and hopefully also have some time to make progress on `union` semantics. -After exploring [a "validity"-based model]({{ site.baseurl }}{% post_url 2017-08-11-types-as-contracts-evaluation %}) last year, I am going to be looking at an "alias"-based model this year. +After exploring [a "validity"-based model]({% post_url 2017-08-11-types-as-contracts-evaluation %}) last year, I am going to be looking at an "access"-based model this year. That's the kind of model @arielb1, @ubsan and others have been proposing, and I am going to build on top of their work and hopefully come up with something we can actually implement a checker for -(staying true to the [vision I laid out previously]({{ site.baseurl }}{% post_url 2017-06-06-MIR-semantics %}) that we should have an executable operational semantics for MIR, including its [undefined behavior]({{ site.baseurl }}{% post_url 2017-07-14-undefined-behavior %})). -Expect a blog post soon for what I mean by "validity"-based vs. "alias"-based, and for a first draft of such an "alias"-based model. +(staying true to the [vision I laid out previously]({% post_url 2017-06-06-MIR-semantics %}) that we should have an executable operational semantics for MIR, including its [undefined behavior]({% post_url 2017-07-14-undefined-behavior %})). +Expect a blog post soon for what I mean by "validity"-based vs. "alias"-based, and for a first draft of such an "access"-based model. Until then, stay tuned!