Thoughts on what a next Rust compiler would do
matklad.github.io
Thoughts on what a next Rust compiler would do
1–10 of 147 posts
Re: Thoughts on what a next Rust compiler would do
#2All of this sounds fantastic.
I can't donate my time, but I'd be happy to donate money to anyone taking on this effort.
On that note, I'm looking for more Rust crates and maintainers to donate to. I just started paying Bevy, and I'm looking for more areas of the Rust ecosystem that need it.
This language brings me immense business and personal value, and I'm happy to give back.
Re: Thoughts on what a next Rust compiler would do
#3All of this sounds fantastic. I can't donate my time, but I'd be happy to donate money to anyone taking on this effort. On that note, I'm looking for more Rust crates and maintainers to donate to. I just started paying Bevy, and I'm looking for more areas of the Rust ecosystem that need it. This language brings me immense business and personal value, and I'm happy to give back.
Web3 or something useful?
Re: Thoughts on what a next Rust compiler would do
#4I say this with great respect, but the thing keeping me from Rust isn't the compiler, it's the language.
Re: Thoughts on what a next Rust compiler would do
#5How much faster can the compiler be? This is the top issue with rust IMHO - compile times are real bad.
Re: Thoughts on what a next Rust compiler would do
#6All of this sounds fantastic. I can't donate my time, but I'd be happy to donate money to anyone taking on this effort. On that note, I'm looking for more Rust crates and maintainers to donate to. I just started paying Bevy, and I'm looking for more areas of the Rust ecosystem that need it. This language brings me immense business and personal value, and I'm happy to give back.
Web3 or something useful?
[deleted]
Re: Thoughts on what a next Rust compiler would do
#7I say this with great respect, but the thing keeping me from Rust isn't the compiler, it's the language.
What about the language do you dislike? It's a strongly typed Ruby with generics.
Edit: trait-based OO is a breath of fresh air compared to tree-style class inheritance. Super flexible without having to overthink.
Immutable by default is reassuring, Option/Result are fantastic null/exception replacements.
Enums and match blocks are powerful and gracefully help ensure handling of all cases, have nice syntax, and work well for a systems language.
Re: Thoughts on what a next Rust compiler would do
#8How much faster can the compiler be? This is the top issue with rust IMHO - compile times are real bad.
If you consider how much LLVM instructions are emitted and how much time Rust spends linking, the potential for speedups seems very significant.
Re: Thoughts on what a next Rust compiler would do
#9I say this with great respect, but the thing keeping me from Rust isn't the compiler, it's the language.
What about the language do you dislike? It's a strongly typed Ruby with generics. Edit: trait-based OO is a breath of fresh air compared to tree-style class inheritance. Super flexible without having to overthink. Immutable by default is reassuring, Option/Result are fantastic null/exception replacements. Enums and match blocks are powerful and gracefully help ensure handling of all cases, have nice syntax, and work…
Huh? Rust shares very little with Ruby??? Are you thinking Crystal?
Re: Thoughts on what a next Rust compiler would do
#10I say this with great respect, but the thing keeping me from Rust isn't the compiler, it's the language.
I felt this way about Rust for a really long time, but after sitting down and doing a few projects with Rust I've really come to appreciate how much the language stops me from being a dumbass.