Mostly Grey former ginger with a preference for Rust. Leads wg-rustup, sorry about the mess. He/Him or They/Their Now @kinnison@fosstodon.org too

Manchester
Joined December 2008
Filter
Exclude
Time range
-
Near
If any @rustlang people were having trouble with Rustup 1.24.1 and memory allocation, 1.24.2 is now out and should fix things - blog.rust-lang.org/2021/05/1…
2
Replying to @fanf
I'd start with doing the cleanest looking code, and then only worry if the optimiser isn't doing what you want.
Replying to @frabcus
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.
2
Replying to @frabcus
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.
1
1
Replying to @jtopper
Wikipedia says... Although shagging is not considered to be dangerous,[several freak injuries have occurred as a result of engaging in it.
1
Replying to @fanf
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.
1
Replying to @fanf
Good point, I'll faff a bit more, and I guess I'll sort a newer nightly then.
Replying to @fanf
Hmm, I get paste.rs/TsS which suggests that the problem was already likely fixed. What toolchain are you using? I'm on 1.52.1
1
Replying to @fanf
When you're otherwise done, point me at your codebase and I'll see if I can dig something out :D
1
Replying to @fanf
If you can construct a minimal example of it being wrong, please file a bug. The clippy people will appreciate it.
1
Replying to @fanf
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
1
Replying to @mjg59
I fear you may now be at the 'air is a fundamentally bad conductor of electricity' stage of dealing with networking :(
1
2
Replying to @dsilverstone @fanf
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)
1
Replying to @fanf
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
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 :(
1
Replying to @fanf
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
Replying to @nick_r_cameron
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 :/
4