trying something a little more adventurous with Rust: yet another version of my dns-trie adventurous because it will need a little bit of unsafe{} to be competitive with the C version
2
5
currently trying to work out how to do this in stable rust: there is Vec::from_raw_parts() BUT NOT Vec::into_raw_parts() 😭
2
1
hmm actually i want slice::from_raw_parts which avoids having to worry about the compiler implicitly dropping the vec when i don’t want it to
1
ugh, having moaned at length about if{}else{} being so much more bulky than ?: i will now moan at length about how a missing ; is so much more tricky than a return keyword
2
1
Out of interest have you got rust-analyzer sorted in your development environment? I find that with all the IDE badgers turned on, type inlays, etc. that all the more terse syntax like `?` and the last-expression-is-value stuff makes things so beatifully readable.
1
lsp-mode had too many incomprehensible flashing lights and was easy to confuse badly enough that it locked up emacs, so i went back to rust-mode
1
Replying to @fanf
Aah most people I know who Rust seem to use vim or vscode, both of which seem to have competent lsp stuffs. Pity emacs hasn't got there yet then :(

May 12, 2021 Β· 7:54 PM UTC

1
Replying to @dsilverstone
in one case i did a git thing which confused rust-analyzer with knock-on effects for emacs so lsp-mode wasn't entirely to blame if i don't like lsp-mode i doubt i will like vscode (i tried vscode but it has the wrong keybindings so it seemed like more trouble than it's worth)
1
Yeah I switched from emacs to vscode a few years back and my vscode keybindings had a lot of emacsy things in for a while as I retrained fingers after decades of emacs :D I still emacs for C code tbf :D
1
1
more replies