Recent searches
Search options
One thing I particularly like about Rust — which I’m very new to — is how thoughtfully the compiler errors and warnings have been designed. It not only diagnoses and explains the problem: it provides a possible solution. Genius.
This is the essence of good design: it’s compassionate, anticipating the needs and wants of another person. I can’t think of another language that does anything like this. Certainly not Swift, not that I’m bitter.
@caspar it's made such a difference for my programming workflow. For python I wrote a few lines, run code, write a few more, run code...
Rust, I can be bashing away for an hour, then run and even if a hundred errors came back it wouldnt bother me as I know I can work with the compiler to fix it.
Rust is good, the tooling is amazing.
@divclassbutton Exactly! It’s a feature all compilers (& interpreters) could and should emulate.
@caspar Yes, as someone learning Swift, it continually disappoints me that Apple hasn’t applied their overall company ethos of user-centric design to Xcode’s compiler errors and warnings.
Hard to imagine text less user friendly, less intuitive and requiring more of a secret-decoder-ring than the Swift compiler’s responses. My hope is after SwiftUI matures, Apple directs more of those resources into applying what you’ve noted Rust’s compiler has accomplished for their developers.
@caspar Since it knows so much about what’s going on and what to do about it, why doesn’t it offer to go ahead and fix it? The toolchain in Xcode for Swift and Objective C do that.
@godofbiscuits @caspar that’s more of an IDE task than a compiler one.
@MyLittleMetroid @caspar yes and no. It’s the compiler front end that’s determining code errors. And if you’re contending that Swift as a language isn’t up to Rust’s error reporting, why is it up to the Rust dev to fix everything?