Yes and no.

And you clearly missed the enums part.

most types are not thread-safe.

Safe rust is thread-safe in the sense that you can’t have runtime thread unsafely. If we are going to ignore the role of compile-time errors, then literally nothing is safe.

Also, what is “most”? Can you source that claim?

great article!

Is it?

I didn’t read past the first sentence:

The Arc type is Rust’s thread-safe smart pointer

This is horrible in my view. All types that implement Deref and/or DerefMut can be called smart pointers, and everything is “thread-safe” in safe Rust.

If I had to call something “Rust’s thread-safe smart pointer”, it would be the actual references &T/&mut T where T: Send + Sync.

Digression: All the traits involved like the 4 mentioned above point to the C++ centric concept of smart pointer not mapping cleanly to Rust semantics imho. But that’s a long lost battle.

Let’s see what the official Arc docs say:

A thread-safe reference-counting pointer.

Will you look at that! An actually accurate short description that is already available.

While not widespread, there is already a small myth out there that paints Rust as if it’s Swift-like, a ref-counting centric language.

You can custom serialize (timestamp, tz) or timestamp, offset or (timestamp, tz, offset), no?

Ironically, that was a part of a back-and-forth I had with burntsushi (jiff dev) right here on lemmy.

It’s called a spam re-post.

Change your name to Err::<!,!>(return).unwrap()

Nothing of significance will actually happen. The crate is too deeply intrenched in the ecosystem. And the little maintenance needed will be easily picked up.

Coming from C not C++, I actually didn’t like chrono at first, but grew to be okay with it, and it gets the job done.

Fastrand is not cryptographically secure

That’s not relevant when it’s a question of interface.

fastrand has a single Rng struct that drives everything else. Was the option to replace the implementation details of this struct explored? No idea.

Ctrl-F fastrand (0 results)

I had to stop reading very early. Sorry, but if you’re going to do this topic, at least acknowledge the other very popular randomness crate, and argue why it wasn’t good enough for what you wanted.

The test suite passes, so it’s 100% memory safe according to zig guidelines and standards.

This is the way.

I think the other user meant that ls output is not supposed to be treated as parsable, because the tool doesn’t offer any guarantees in that regards.

Shells have built-in support for globbing files anyway. xargs is also not needed. If someone is allergic to using a shell for loop, find always had -exec with ; instead + which wouldn’t trip on too many arguments.

Actually, I didn’t notice your use of clone() which is even worse.

Here is what I had in mind. One can put the T: Default bound on the wrappers themselves to simplify, or add potentially expensive transformations for non-Default types.

Using cells in your solution is smelly, when you can simply use two transparent wrappers with Ref or RefMut access, so you have actual compile-time checking instead of janky checking at runtime (which is also not zero-cost).

The allow/deny variants could themselves hold & or &mut references too if we are going with that route. But it all depends on the precise problem OP is having and what is the best workable solution for it looks like.

Can you clarify/expand on what you mean.
Are the other objects of the same type (so are indeed Self)? Are they in the same Vec or a different Vec or from different Vecs?
Are all the T’s in your post the same?
…etc

Thank you for spamming info about a 6 month old model just because it was posted in another instance you don’t want people to use.

I replied on-topic there.

There should be a rule against low quality posts.

Vibe-coded trash + outdated models.

Wouldn’t have expected anything better from a trash website.

translates to assembly code with a very predictable pattern.

the portable assembly meme

🤣🤣🤣🤣🤣🤣🤣

⚠TRIGGER WARNING⚠ two tokio-rs repos (this and toasty) have AGENTS.md files.