Zachary Dremann

I can't count the number of times I've seen this: "Now that I've disabled the server from starting, the app runs without issue. It is now complete and production-ready!"

it can be really difficult to work with people who think theyre always the smartest guy in the room, especially for me, the actual smartest guy in the room

how to deactivate torment nexus

torment nexus deactivation tutorial

torment nexus deactivation tutorial working 2025

deactivate torment nexus no survey

Strictly speaking, you _can_ add new implementations in a non-breaking change, but they would have to be subtypes of an existing subtype of the sealed interface.

Yes, it is. So in Kotlin, "*non-exhaustive enums* are equivalent to *sealed interfaces*" isn't true, Kotlin sealed interfaces are equivalent to a normal, exhaustive enum in Rust.

Maybe what kotlin calls sealed interfaces are actually something else from a type-theoretic world, but kotlin's sealed interfaces _can_ promise that you won't add a new implementation, which does allow compiler checked exhaustive pattern matching: pl.kotl.in/iOXs1juXW

Today, we’re announcing the preview release of ty, an extremely fast type checker and language server for Python, written in Rust.

In early testing, it's 10x, 50x, even 100x faster than existing type checkers. (We've seen >600x speed-ups over Mypy in some real-world projects.)

Thanks for your thoughtful handling of the situation, Dirkjan and the rest of the rustup team.

FWIW we Rust folks should be a little more forthcoming in saying that the load is not zero—but also that that's fine, the benefits are worth it. I'm worried saying zero load burns credibility

Effectively, because of this, yes, unwrap can be a footgun. But 90+% of your functions don't need to handle options, unlike go, where every pointer is implicitly an option.

Because I can take Option<&T> in one function, and handle the None case, and all the functions it calls can take &T, and statically know they don't need to check for null, even 10 layers away in a helper. If I take a pointer in go for my helper, I either check for null, or doc it expects non null

Compiler Explorer - Rust (rustc 1.84.0) // Type your code here, or load an example. pub enum Feature { Enabled, Disabled } // As of Rust 1.75, small functions are automatically // marked as `#[inline]` so they will not show up in ...

You probably want to enable optimization, by passing `-C opt-level=3` when comparing assembly, even more things will end up optimized away. godbolt.org/z/Gh3jnMEdY

Alright, everyone who uses YouTube and complains about the algorithm not showing you what you're subscribed to -

I present this magic link. This will take you to the subscriptions feed which is only things you are subscribed to.

www.youtube.com/feed/subscri...

Implement `ByteStr` and `ByteString` types by joshtriplett · Pull Request #135073 · rust-lang/rust Approved ACP: rust-lang/libs-team#502 Tracking issue: #134915 These types represent human-readable strings that are conventionally, but not always, UTF-8. The Debug impl prints non-UTF-8 bytes usin...

I'm super excited to see byte string types coming soon to a Rust standard library near you!

github.com/rust-lang/ru...