The push method could return `Ok(())` when it succeeds and `Err(x)` when it fails. Since `Result<T, U>` is marked #[must_use], it forces the caller to handle the error case. Rust as a language is well-suited to writing low-level, robust code. The non-core stdlib is the issue.
-
-
Much more of the standard library could have been available for lower-level use. There could have been a collections and io library usable without those design decisions, etc. It was a very explicit design decision to have such lackluster low-level stdlib and ecosystem support.
2 replies 0 retweets 1 like -
Rust gained support for fallible allocation recently.https://github.com/rust-lang/rfcs/pull/2116 …
2 replies 0 retweets 1 like -
Not a fan of how any of this stuff ended up at all. :\ Seriously regret wasting so much time contributing to the Rust compiler / standard library now. It was so close to ending up as a great language for low-level use but the standard libraries missed the boat completely.
2 replies 2 retweets 6 likes -
Replying to @CopperheadOS @whitequark and
I feel your pain. I was very excited from Rust, but after experiencing it from the position of Alpine package maintainer, I’m very disappointed, mainly because of Cargo. I wish someone took great concepts from Rust and implement it with minimalism and correctness in mind.
1 reply 1 retweet 4 likes -
Replying to @JakubJirutka @CopperheadOS and
What are your issues with Cargo?
1 reply 0 retweets 0 likes -
Replying to @whitequark @CopperheadOS and
Cargo is bloated everything-but-kitchen-sink. It introduces double chick-or-egg problem to Rust – you need cargo and rustc to build cargo and the same to build rustc.They don’t even provide static cargo for bootstrapping.Using git as pkgs index is horrible idea, it’s slow as hell
2 replies 1 retweet 2 likes -
Replying to @JakubJirutka @whitequark and
They made Cargo an inherent part of Rust, but it’s being developed as some hipster JS project.
2 replies 1 retweet 0 likes -
Replying to @JakubJirutka @whitequark and
Moreover, a week ago I’ve packaged the Crystal language, which is also self-hosted and based on LLVM, so now I have some comparison. It was so easy to bootstrap Crystal on musl, even to a different arch! Can’t say that about Rust, not at all, it was like hell.
0 replies 1 retweet 3 likes
80%? Where did you get that figure?
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.