Conversation

Notices

1. Embed this notice
   esmevane, sorry (ironchamber@mastodon.esmevane.com)'s status on Sunday, 17-Nov-2024 11:13:00 JST esmevane, sorry

   in reply to

   • yosh

   @yosh I think there’s a big barrier in technical writing that is mostly jargon, and I don’t know if it’s deliberate or defensive or what.

   Or maybe it’s just plain trying to explain something after going so deep on a problem that the author forgets where they were when they started trying to figure it out to begin with?

   • Embed this notice
     yosh (yosh@toot.yosh.is)'s status on Sunday, 17-Nov-2024 11:13:02 JST yosh

     Saving computer folks a search as to what some C/C++/Google folks mean by certain terms:

     - “temporal safety”: no use after free / double free
     - “spatial safety “: no out of bounds accesses

     I had to look these up, because honestly: these are pretty confusing terms. I wish they would at least consistently qualify these as: “{temporal,spatial} memory safety”.

     There are a lot more non-memory related uses of the word “temporal” when it comes to safety (e.g. Temporal Logic of Actions - TLA, etc.)