Rust and Linux enthusiast
There are kinks to fix that being confusing...
There are kinks to fix that being confusing...
Just not used in the preview window.
Just not used in the preview window.
(Also I'm relatively sure it should be possible to add a size limit to that completion window)
(Also I'm relatively sure it should be possible to add a size limit to that completion window)
This mpreg was teamwork!
This mpreg was teamwork!
I am the energy drink!
I am the energy drink!
(Or more specifically great advice when learning any skill.)
(Or more specifically great advice when learning any skill.)
Hard to know which objects to keep if you don't have any GC roots...
Hard to know which objects to keep if you don't have any GC roots...
(Though as consequence I have an extremely hard time at actually *translating* words from and to english)
(Though as consequence I have an extremely hard time at actually *translating* words from and to english)
Dictionaries are often relatively bad at capturing the nuances of connotations.
Dictionaries are often relatively bad at capturing the nuances of connotations.
Like
"we're using [fallback] in lieu of [ideal]" and
"we're using [fallback] instead of [ideal]"
*basically* mean the same thing.
The only difference is probably that "in lieu of" has a stronger connotation that is implying the "fallback/ideal" split.
Like
"we're using [fallback] in lieu of [ideal]" and
"we're using [fallback] instead of [ideal]"
*basically* mean the same thing.
The only difference is probably that "in lieu of" has a stronger connotation that is implying the "fallback/ideal" split.
I recently had problems on linux with terminals not supporting dead keys.
(Like pressing having to press ` twice to actually type it or `a to get à)
I recently had problems on linux with terminals not supporting dead keys.
(Like pressing having to press ` twice to actually type it or `a to get à)
A value that is in scope and not dropped counts as "used" to me.
But yeah, I wasn't really clear enough about that 🙂
A value that is in scope and not dropped counts as "used" to me.
But yeah, I wasn't really clear enough about that 🙂
The compiler is *probably* not acting on it, but still we all know how scary undefined behavior chains can get like if the compiler wants to use them...
The compiler is *probably* not acting on it, but still we all know how scary undefined behavior chains can get like if the compiler wants to use them...
Nothing else are you doing when you are casting `&'a _` to `*const _`.
The biggest danger are "unbound" lifetimes, where the lifetime ends up being entirely determined by its usage.
Nothing else are you doing when you are casting `&'a _` to `*const _`.
The biggest danger are "unbound" lifetimes, where the lifetime ends up being entirely determined by its usage.