3 ms·
Hadn't thought of that potential benefit to the rust-analyzer work: I could get borrow errors upfront even if there are irrelevant errors in other areas of code
by epage 7y ago
Hadn't thought of that potential benefit to the rust-analyzer work: I could get borrow errors upfront even if there are irrelevant errors in other areas of code.
(borrow checker seems like it is one of the last phases).
- woah 7y agoThat’s how you know you’re reaching the light at the end of the tunnel, when the borrow checker errors start showing up
- empath75 7y agoThat’s usually when I give up and start writing go, tbh.
- echelon 7y agoDo you have to dump on Rust because of its learning curve? It isn't even that bad. It's not like Golang doesn't have warts of its own. I have a hard time believing you make this choice often or "usually". This seems like flat out prejudice.
- galangalalgol 7y agoIf go was fast enough why didn't you start out using it, or some other language that is 3x slower than rust but has gc and comfy ergonomics. C#, clojure, julia, ocaml( if you dont need threads). Or just plane Java.
- _bxg1 7y agoI've started associating a shower of warnings with "success", because those only appear once all the errors have been taken care of
- nirui 7y agoOr, in my case, it tells me why I have to restructure my code :( I mean, an early warning, before I actually made those mistakes would help a lot, if it can be done that is :)