News for hackers. Stuff that matters.
Re:Go: Ten years and climbing by pcwalton on Friday September 22, 2017 @03:09AM (#15310005)
We aren't talking about autocompletion. The post upthread describes "the tools to ensure...data integrity": i.e. type system or static analysis features to prevent bugs.

That said, if you're trying to argue that autocompletion is more difficult to implement for Rust compared to Go because Go is simpler by some metric, then I disagree there too. Any static language (well, one that doesn't intertwine parsing and semantics like C++ does) can support autocompletion with comparable levels of implementation effort.

Re:Go: Ten years and climbing by e3b0c on Friday September 22, 2017 @03:46AM (#15310141)
Then I am curious about what makes RLS or the alike so hard to onboard? Common IDE features like reliable and responsive "jump to definition", "Find all references" and "Renaming symbols" are 90% of all I would ask for. Do Rust devs have less attention to the area?
Re:Go: Ten years and climbing by steveklabnik on Friday September 22, 2017 @10:33AM (#15312513)
Those three things already work in the RLS. And more: https://www.ncameron.org/blog/what-the-rls-can-do/
Re:Go: Ten years and climbing by mswift42 on Friday September 22, 2017 @11:05AM (#15312819)
Is there an editor that supports jump to definition for macros?
Re:Go: Ten years and climbing by steveklabnik on Friday September 22, 2017 @11:37AM (#15313127)
I don't know. I have a hunch that lots of macros still will be better with the new macro system, but we'll see.

Anyway, regardless, there's certainly more work to do! And it's being actively developed quite heavily. For example, it will be on stable Rust very soon.

Re:Go: Ten years and climbing by mswift42 on Friday September 22, 2017 @02:24PM (#15314505)
Thanks.