Stream: t-lang/wg-unsafe-code-guidelines

Topic: racy-read / volatile / untrusted memory / freeze


RalfJ (Oct 09 2019 at 15:21, on Zulip):

@nikomatsakis seems like since we talked about this just last week, another thread was opened related to this group of topics that keep coming up here. we don't have a dedicated tag for them yet as I am not sure what a good term would be; I am talking about a subset of https://github.com/rust-lang/unsafe-code-guidelines/labels/T-memory. specifically:

RalfJ (Oct 09 2019 at 15:22, on Zulip):

we have plenty of discussion on those, so much that we cannot expect anyone to read all of it. so what we need is a good summary, ideally one we can even get UCG consensus on (so not just one more of my WIP documents)

RalfJ (Oct 09 2019 at 15:22, on Zulip):

I'd love to work on that but I have zero time that I can commit here right now, I'm afraid

RalfJ (Oct 09 2019 at 15:22, on Zulip):

but we can at least maybe make this our next official "topic of discussion" or so? Cc @WG-unsafe-code-guidelines

RalfJ (Oct 09 2019 at 15:23, on Zulip):

we still have a lot of write-up to do though for validity invariants

nikomatsakis (Oct 11 2019 at 20:47, on Zulip):

@RalfJ that's a good idea

nikomatsakis (Oct 11 2019 at 20:48, on Zulip):

I'm not sure how much time I have either

nikomatsakis (Oct 11 2019 at 20:48, on Zulip):

well I know how much

nikomatsakis (Oct 11 2019 at 20:48, on Zulip):

but I do think it's a good topic and a place we could get consensus

simulacrum (Oct 11 2019 at 21:15, on Zulip):

for the write-up part, is the knowledge just scattered, or in-heads-only? i.e., can someone help out with that "easily" in some sense?

RalfJ (Oct 12 2019 at 14:00, on Zulip):

for validity most of the knowledge is in the issues: https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aissue+is%3Aopen+label%3AT-validity

Last update: Nov 20 2019 at 11:25UTC