From f5cc045de814c793e7b927beafa405ee0a8923a1 Mon Sep 17 00:00:00 2001 From: Ralf Jung Date: Tue, 7 Aug 2018 19:17:32 +0200 Subject: [PATCH] fix typo --- personal/_posts/2018-07-11-research-assistant.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/personal/_posts/2018-07-11-research-assistant.md b/personal/_posts/2018-07-11-research-assistant.md index 24b3f71..0641bef 100644 --- a/personal/_posts/2018-07-11-research-assistant.md +++ b/personal/_posts/2018-07-11-research-assistant.md @@ -10,9 +10,9 @@ I don't really know what a "research assistant" is, but I am going to continue t -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 "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]({% 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 "alias"-based model. +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! -- 2.30.2