3 ms·
Why get hung up on one tool? Just write Rust code as if it were plain text. It's a statically typed language, so the compiler will check your code before runnin
by ahmedalsudani 8y ago
Why get hung up on one tool? Just write Rust code as if it were plain text. It's a statically typed language, so the compiler will check your code before running it, and your can run rust fmt to fix formatting.
Maybe one day you can shun the darkness and embrace emacs ;) all your problems disappear on that day
- Waterluvian 8y agoA massively important tool I use for learning a language and libraries is autocomplete. Emacs takes a day to master? Awesome!
- always_good 8y agoWell, that's always an option, so it isn't really advice. It's already what you have to do when the tooling support is bad. It's the poorest when an editor can instead inline its output of static analysis. Integration has a lot of benefits like tell you the inference of intermediate types. "Don't care about good integration" isn't really advice. It's like people who brag about syntax highlighting. The 99.9% rest of us consider it a good tool that improves our workflow.
- ahmedalsudani 8y agoNo dispute integration is nice, but it is not working properly from what my parent comment was saying. Your options are to wait for it to improve, fix it yourself, or change your tools/workflow. Some people seem to have had an allergic reaction to my comment. Maybe it's the emacs mention, which was tongue in cheek. Oh well ¯\_(ツ)_/¯ I'll leave it as it is... for this is a righteous battle!
- always_good 8y agoI don't see a righteous battle. You mentioned Emacs as a solution which has a Rust plugin that has problems like most other Rust tooling. Yes, Rust's tooling landscape is immature and still a work in progress. Obviously you can just forgo editor integration all together. But you can do that in any editor.
- guscost 8y agoThe fancy tools can check your code as you write it and highlight problems inline so you don't have to switch context in order to fix them. This saves time in any language, but static analysis with Rust is unusually powerful so tightening that feedback loop pays serious dividends (when it works). I'm not saying emacs and vim aren't really cool technologies. But why would a person who cares about optimizing keystrokes and crafting macros dismiss a tool that optimizes debugging and refactoring? I spend a heck of a lot more time staring at code than I do typing it, and if the reverse is true for you then you're some kind of savant and/or (more likely) you're writing too much code and reading too little of it.
- IshKebab 8y agoRobust autocomplete is probably the most important tool for a language there is though. It's a shame that Rust doesn't have it and I'm slightly concerned that in never will - type inference means in lots of places there simply isn't enough information to do autocomplete properly.