It took me way too long to realise that Arc<Mutex<T>> is basically a way to create multiple &mut T references (with runtime constraints).
This means that you can use plain &T and &mut T in the vast majority of your code. Most code doesn't need to care there's a mutex.
miniblog.
Related Posts
I'm playing with Zeal/Dash so I can view stdlib docs offline.
(I've been coding on public transport recently, without a reliable data connection.)
Anyone have tips for making the most of this setup? AFAICT docsets are basically HTML underneath.
RISC-V seems like a great example of "commoditise your complements". If you're getting value higher in the hardware or software stack, a royalty-free ISA is valuable.
Creating an ISA is a ton of work. Once it's basically viable, it creates interesting opportunities.
I've been learning more about refactoring operations ("code actions") in the Language Server Protocol and they're more limited than I realised.
An action is basically a name and an edit. There's no scope for prompting the user or offering GUI options.