Better Error Message For Incorrect -> Arrow In Closure?

[JimLynchCodes]

Coming from the TypeScript world it's easy to accidentally add an arrow "->" when doing a one-liner closure, but I feel like this is a very cryptic error message that it gives...

Is there any way to have it suggest , "if you meant for this to be a closure, remove the arrow"?

Thanks! 👍 🦀

[lnicola]

But.. expected a type is the right error here.

[ChayimFriedman2]

If you use => (which is what JS use), rustc will say return types are denoted using `->` , which is quite nice even if not perfect, and I guess they will be happy to improve it even more.

But for rust-analyzer, our errors are quite bad, and doubly so for parsing errors. This is quite sad as errors from the IDE are usually the first thing users see and not cargo check (although we do show rustc errors too), but I'm not sure at this stage of development of rust-analyzer we want to bother with perfectioning our errors, something rustc has been doing for years. I think it is more important now to get full language coverage (both for IDE services and for diagnostics). Ideally, we would just reuse rustc's rich errors, but I'm not convinced this is feasible. If not, then eventually I do believe we will come to improve our errors, but I don't want to invest in it now.