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

Topic: meeting 2018-11-14


nikomatsakis (Nov 14 2018 at 21:21, on Zulip):

So are we going to meet tomorrow @WG-unsafe-code-guidelines ? It's not in our calendar invite.

I think maybe we should change the invite to every week. Thoughts?

Also, do we have a proto agenda?

Nicole Mazzuca (Nov 14 2018 at 21:21, on Zulip):

I would like to discuss unsafe extern blocks

Nicole Mazzuca (Nov 14 2018 at 21:22, on Zulip):

also, converting from unsafe fn() to fn()

Nicole Mazzuca (Nov 14 2018 at 21:24, on Zulip):

also, contravariant and non-contravariant function pointer casts

nikomatsakis (Nov 14 2018 at 21:27, on Zulip):

Hmm. I would sort of like to stay focused on the discussion area -- some things on my mind:

Some other things:

Nicole Mazzuca (Nov 14 2018 at 21:40, on Zulip):

well, the latter two are specifically on the function pointer RFC

Nicole Mazzuca (Nov 14 2018 at 21:40, on Zulip):

i.e., "what can you do with a function pointer and still call it"

Nicole Mazzuca (Nov 14 2018 at 21:41, on Zulip):

also, are function pointers presumed valid to call under their current type?

nikomatsakis (Nov 14 2018 at 22:37, on Zulip):

ok, sounds good

nikomatsakis (Nov 14 2018 at 22:37, on Zulip):

I need to catch up! :)

RalfJ (Nov 15 2018 at 07:35, on Zulip):

the date in the topic is wrong though, isn't it? The meeting wasnt yesterday?^^

RalfJ (Nov 15 2018 at 07:38, on Zulip):

also, are function pointers presumed valid to call under their current type?

I think this has to be part of the safety invariant (because we let safe code do it), but cannot be part of the validity invariant (because it is not decidable, and hence shouldn't be part of our definition of UB)

Last update: Nov 19 2019 at 17:35UTC