Live data from Hacker News

Visualize Ownership and Lifetimes in Rust

github.com

61–64 of 64 posts

Re: Visualize Ownership and Lifetimes in Rust

#61
post #54

Earlier quoted context omitted.

It's totally normal except for C/C++ toolchains on Linux . C/C++ compilers are managed this way on MacOS, Windows, and by most embedded toolchains. Why don't you want your toolchain managed outside your distro? Don't you want your software to run outside your distro?

Longing for a more stable world doesn't sound very weird to me. Maybe core Rust development will slow down in the future.

Well, you're never going to have a stable world when you're constantly pulling in updates to your dependencies. In any language.

And if you stop updating those, you stop needing rustc updates.

Re: Visualize Ownership and Lifetimes in Rust

#62

Earlier quoted context omitted.

Longing for a more stable world doesn't sound very weird to me. Maybe core Rust development will slow down in the future.

Well, you're never going to have a stable world when you're constantly pulling in updates to your dependencies. In any language. And if you stop updating those, you stop needing rustc updates.

Right, but in the rest of the world it's more common for the libraries to support a wider range of compiler and language versions. The culture as of yet of Rust, is that more libraries require the newest compiler.

Re: Visualize Ownership and Lifetimes in Rust

#63

Earlier quoted context omitted.

Well, you're never going to have a stable world when you're constantly pulling in updates to your dependencies. In any language. And if you stop updating those, you stop needing rustc updates.

Right, but in the rest of the world it's more common for the libraries to support a wider range of compiler and language versions. The culture as of yet of Rust, is that more libraries require the newest compiler.

But that wider range by itself means nothing. It only matters in the context of what it enables and how well it enables it.

Re: Visualize Ownership and Lifetimes in Rust

#64
post #54

Earlier quoted context omitted.

It's totally normal except for C/C++ toolchains on Linux . C/C++ compilers are managed this way on MacOS, Windows, and by most embedded toolchains. Why don't you want your toolchain managed outside your distro? Don't you want your software to run outside your distro?

Longing for a more stable world doesn't sound very weird to me. Maybe core Rust development will slow down in the future.

I came over to Rust from C++ and I really don't want core Rust development to slowdown. The changes you see are mostly useful APIs in std.

Compare to C++, where using a new std API/type can take a literal decade and might not be backwards compatible on targets even once compiled.

Stability is only useful if it gets in the way of reliability and convenience. That's true in C/C++ because of the compilation and development model. In Rust those problems don't exist, so "stability" of std largely gets in the way.

Post reply on HN