nomicon VS clojure-style-guide

it’s even written by the same person that wrote the Nomicon (the guide to the dark arts of unsafe)

If you want to dive deeper you can always have other options but now there are concrete cases, if you want to do low level thing https://doc.rust-lang.org/nomicon/ while if you want multi thread/concurrency stuff https://marabos.nl/atomics/ . There are many many books so you will have to point yourself to what you want

Nonononono. SeqCst is the most error prone memory order: https://github.com/rust-lang/nomicon/issues/166

Hope this helps. For more details, see the Rustonomicon. I referenced the subtyping chapter here extensively.

Nice video! Glad I could help out. This stuff is hard, and I'm still learning a lot about it myself even years later. The Rustonomicon is a great read if you haven't already.

Have you got a moment to read through the good book , after reading through this perhaps try the Rustonomicon.

That is not what UB means. Undefined Behaviour is behaviour that the compiler is allowed to assume will never happen, and which can consequently cause miscompilations due to optimisation passes gone wrong if it does in fact occur in the source code.

It's true that Rust does not have a written specification that clearly delineates what is and isn't UB in a single place. But:

1. UB is impossible in safe code (modulo bugs in unsafe code)

2. There are resources such as the Rustinomicon (https://doc.rust-lang.org/nomicon/) that provide a detailed guide on what is and isn't allowed in unsafe code.

In practice, it's much easier to avoid UB in Rust than it is in C++.

However, this is a wide topic out of scope for a Reddit comment, so maybe just read the Rustonomicon. It explains everything about data handling in Rust.

The ownership model & borrow checker makes rust a bit of an awkward language in which to write complex data structures like trees and graphs. It can be done - since you can always use raw pointers & unsafe code when you absolutely need to to treat rust like C. But the language fights you, and the community can get a bit moralistic about this sort of thing. The rust nomicon is a fantastic resource for learning the limits of the borrow checker, and where and how to use unsafe code correctly. You will need unsafe less than you think you will, but sometimes you will have no choice.

Fixed link to that style guide entry: https://guide.clojure.style/#opt-commas-in-map-literals

Per that style guide, the above map would be formatted like this (on HN, just indent by two spaces):

  {:a 1

As for the broader question of Clojure style, there are style guides like https://github.com/bbatsov/clojure-style-guide and tools like clj-kondo to help learn and reinforce important practices.

Basically, you learn the expected places to put whitespace, make sure to edit your code accordingly and all of the parens will be automatically closed and adjusted. Using parinfer—which you can also combine with the more traditional paredit—makes writing Clojure code a lot like writing Python.

Also, there are guidelines, the styleguide, clj-kondo, kibit etc. And if you don't review your interns/juniors code to teach them good practices - you're doing it wrong (well, this one is true for any practical PL out there).

Another good resource is https://guide.clojure.style/ -- the (unofficial) community style guide for Clojure.

It's not an answer to your question but i can refer you to https://github.com/bbatsov/clojure-style-guide

The same could be said about the "Clojure Style Guide" from the Cider guy. As a matter of fact, there was an issue about it that was quickly declined https://github.com/bbatsov/clojure-style-guide/issues/232

Formatting is not that great, see https://github.com/bbatsov/clojure-style-guide btw