Conversation

Notices

1. Embed this notice
   cliffle@hachyderm.io's status on Friday, 25-Nov-2022 09:11:21 JST cliffle

   Here's an article I've been meaning to write, gauging interest:

   In Java/C/etc a lot of thread safety advice comes down to "always be thread safe because you never know." Synchronized methods, mutexes hiding in data structures, etc.

   #Rust makes it easier to write thread-safe code, but it also makes it _possible_ to write code that _can't_ be used across threads, and thus doesn't have to be thread-safe. This reduces complexity and improves performance by avoiding all that defensive coding.

   • Masanori Ogino 𓀁 repeated this.
   • Embed this notice
     cliffle@hachyderm.io's status on Friday, 25-Nov-2022 09:11:21 JST cliffle

     in reply to

     Thanks for the feedback, folks! I've posted a first version of this article: https://cliffle.com/blog/not-thread-safe/

     This looks at one of my favorite features of Rust: how it enables me _not_ to write all my data structures as thread-safe... and yet still have concurrent programs without data races.

     Less code, less complexity, more reliability. Magic! ✨

     ...well, ok, type systems, but type systems are a sort of magic. ?