What is Rust and why is it so popular?

> I need to go better understand what exactly the language server is doing if the compiler is able to provide all the details.

Converting it from what the compiler knows to the https://langserver.org/ protocol.

The long-term goal is to have the compiler be able to do this directly, but there's some stuff to do in the meantime.

It's kind of how like when Go first bust out on the scene and every org that was "doing DevOps" claimed they had "Go in the building", the reality is you wrote CLI scripts and did 90% of your job in Java or Python. They may mention Rust, but doubt it's what you'll be solving the majority of business problems in.

In my experience, the vast majority are exactly like the error they show. Some are even better. I haven't hit a warning in ages that hasn't been able to be auto fixed by `cargo fix`.

However not all of them are. Back in the pre-async/await days you'd end up with some really gnarly implicit types in some really big functions with lots of returns. Then sometimes you'd make a mistake on one of the returns and the compiler would assume that your mistaken type was the right one & point out all the places where the actually correct type was returned. Then you'd have to go hunt for where you needed to add a `as Box>` to get it to compile again.

I haven't hit any issues like that since I started converting the gnarly stuff to infinitely simplier async/await code, but I have to imagine those kinds of issues are still lurking in other areas where you can't get away from complicated code.

Even with that I whole-heartedly recommend anyone that's thinking about it just go try it out and/or read some of the book. It's a delightful language to work with. I have way more fun working with Rust than I have with any other language. It takes care of so much of the BS that I don't want to have to think about, so I can just think about the interesting stuff.

The nickname works like alias that only shows 3 characters of the name. Before using nickname the code frees the name making both name and nickname invalid. The error here is use after free and one strengths of rust is to detect errors like this.

In C such code would compile, what's worse, it would work and behave correctly most of the time. If your code was more complex (for example using threads) you would get a bug that the code would work fine most of the time, but once in a while it would display garbage.

Some well-liked SF mod got randomly booted due to a CoC powerplay, and then everything exploded. Rules weren't followed correctly, mods getting kicked out or quiting in revolt, all sorts of corporate powerplays and misplays

Basically the whole stack overflow administration is fucked, but also no one really cares because that administration is mostly invisible to the majority of SF users (developers coming from Google). Same way Wikipedia drama has never been cared about by anyone but Wikipedia mods. General pop will only care once the quality of the system degrades

This article however probably has nothing at all to do with that, and is probably authored/published by a team entirely independent of the stack overflow mod administration.