[Pre-RFC] Another take at clarifying `unsafe` semantics

[gbutler]

It also has the additional advantage of containing the good parts of both worlds, I think. Namely, I love how today’s simple one-keyword unsafe catches the reader’s attention, but doesn’t look uglier than e.g. pub fn — it is clear but not disturbing. Compare with Java’s public static final volatile synchronized iAlreadyLostTrackOfTheFuncName()… brrr!)

Yes, I think this, using attributes to denotre the pre/post thing is a much more useful, extensible, and less disruptive direction.

[system]

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.