Pre-RFC: Guarantee that pointers to `OsStr` has the same layout as pointers to `str`/`[u8]`

Are the meeting notes available anywhere? Your linked comment doesn't really get into the "why" of it all. My end goal was to create a path! macro that could be used to build truly cross-platform paths (i.e., that don't on / being a path separator) at comptime, which is unfortunately impossible as of now due to the absence of this guaranteee.