GIF
3
20
155
Conversation
Nice! I do still wish we had holes in Rust… would be super nice for the match arms/patterns ; _ ;
1
4
This Tweet is from a suspended account. Learn more
Yeah, that's what I do - feels a bit hacky though, and can't really put them in patterns. Also can't use them interactively for case splitting etc. like in Agda, Idris, Haskell, etc.
1
1
Like, it's a tad annoying when rust analyzer has to generate code that doesn't type check or even parse 😢
1
One example is function completion, where it inserts a function call with argument names pulled from the parameters (which may not exist in scope). It would be super nice if it inserted a function call with a bunch of holes that you could jump to and fill interactively… 😅
But yeah, still super thankful for all the cool stuff that rust analyzer has already, it makes rust super nice to use! Just would be super neat if they could also pull some of the good ideas from the theorem proving/functional world too! Especially considering Rust's ML roots!
1
Replying to
I personally disable this feature (`"rust-analyzer.completion.addCallArgumentSnippets": false`), as find it more distracting than useful. Parameter info popup and completion, if done right, should work just as good as holes.
Sadly, param info in code is
1
1
Hmm, still seems like it generates broken code though? Like, it produces:
make::use_item(make::use_tree())
rather than something like:
make::use_item(make::use_tree({! !}, {! !}, {! !}))
Same goes for `match`, where this stuff becomes even more useful!
3
Show replies