{{ content }}
<p class="comment">
- Posted on <a href="{{ site.baseurl}}/blog">{{ site.blog.title }}</a> on {{ page.date | date: "%b %-d, %Y" }}. <br>
+ Posted on <a href="{{ site.baseurl}}/blog">{{ site.blog.title }}</a> on {{ page.date | date: "%b %-d, %Y" }}<!--
+ -->{% if page.license %} and licensed under <a href="{{ page.license-url }}" target="_blank">{{ page.license }}</a>{% endif %}. <br>
Comments? <a href="mailto:post+blog-AT-ralfj-DOT-de?subject=Blog post comment: {{ page.title | uri_escape }}">Drop me a mail</a><!--
-->{% if page.reddit %} or <a href="https://www.reddit.com/r{{ page.reddit }}" target="_blank">leave a note on reddit</a>{% endif %}<!--
-->{% if page.forum %} or <a href="{{ page.forum }}" target="_blank">leave a note in the forum</a>{% endif %}!
title: The Scope of Unsafe
categories: research rust
reddit: /rust/comments/4065l2/the_scope_of_unsafe/
+license: CC BY-SA 4.0
+license-url: https://creativecommons.org/licenses/by-sa/4.0/
---
I'd like to talk about an important aspect of dealing with unsafe code, that still regularly seems to catch people on the wrong foot:
title: How MutexGuard was Sync When It Should Not Have Been
categories: rust research
reddit: /rust/comments/6gavfe/how_mutexguard_was_sync_when_it_should_not_have/
+license: CC BY-SA 4.0
+license-url: https://creativecommons.org/licenses/by-sa/4.0/
---
A couple of weeks ago, our ongoing effort to [formalize Rust's type system]({% post_url 2015-10-12-formalizing-rust %}) lead to us actually discovering a bug in the Rust standard library:
title: "Pointers Are Complicated II, or: We need better language specs"
categories: rust research
forum: https://internals.rust-lang.org/t/pointers-are-complicated-ii-or-we-need-better-language-specs/13562
+license: CC BY-SA 4.0
+license-url: https://creativecommons.org/licenses/by-sa/4.0/
---
Some time ago, I wrote a blog post about how [there's more to a pointer than meets the eye]({% post_url 2018-07-24-pointers-and-bytes %}).