lol, I wrote a bit of code and my editor was happy with it, and I was very confused because it looked like there was very obvious reuse of a moved value that shouldn't have worked, but wasn't getting any diagnostics...
Turns out the rust language server was just busted, and I now have about three pages of angry borrow checker to sift through. At least I was right about the code being wrong, I guess.
@lori I would argue yes, because it's mixing ownership and lifetimes in with "plain" type things, so you can paint yourself into much more interesting corners :)
@danderson something you'll slowly get used to is that the borrow checker is another stage in the build process, so it becomes normal to expect another stage after syntax and type correctness - early on it's unusual though, which can be jarring
@raggi Well now rls is just crashing immediately when I try and start it, so once I'm back to code that compiles, that'll be a little side adventure...
@danderson oh no, that sounds awful :( I've had it get stuck on stuff like git branch switches, much like the go one and so on, but i've not seen a crashloop for a few years now
@raggi I expect it's some combination of my hipster environment that's going wrong, as usual. Emacs on nixos with rls being pulled into scope by direnv magic that's monkeypatched back into emacs... I forgive it for not liking where it finds itself 😂
Add comment