the memory technique which works for me is spatial arrangement. Interestingly my mental world manifests as words, and while for much of my life they were just lists I could reorder, these days I've learned to generate mental word clouds.
I'm fortunate that I've known there are strong differences all my life. My mother is strongly prophantasic and my aphantasic lived experience always used to baffle her. She finally 'got it' when I could not describe the house I had just bought without walking around it.
Iiinteresting. Clippy still mentions the submodule name but gets the impl<T>. rust-analyzer's create-default-impl-from-new doesn't insert the submodule name but misses the <T> off the impl.
I would worry that as_cooked_parts could explode if I construct a bmpvec from raw parts which are not heap allocated. You need to document the invariants which the unsafe methods rely on
Actually I vim for email, emacs for C, vscode for markdown/rust/javascript - I remain a disgusting multi-editory person. I still remember the horror of a colleague when I had vim and emacs open on the same perl .XS file to emacs on the top half (C) and vim on the bottom (Perl)
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
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.
If you find such a resource I'd *love* a link. This kind of thing comes up a lot in my workplace and I've yet to find anything truly suitable. Everything I know was picked up by trial/error over the (gulp) decades :/