Rust and Linux enthusiast
Your post made me think there should be a "hug" button and not only the impersonal "like" button, so i made it happen! (ish)
Your post made me think there should be a "hug" button and not only the impersonal "like" button, so i made it happen! (ish)
Let wait and see if someone ruins it.
Let wait and see if someone ruins it.
I hate ABA problems!
I hate ABA problems!
No.
I wont.
You can't make me!
No.
I wont.
You can't make me!
Witness my graveyard!!!
Witness my graveyard!!!
github.com/xkbcommon/li...
github.com/xkbcommon/li...
And I guess my `wc -l` says the same as your `wc -l`
And I guess my `wc -l` says the same as your `wc -l`
Especially when you have `conceal` enabled for it.
(Here an `.luarc.jsonrc` highlighted with neovim as an example)
Especially when you have `conceal` enabled for it.
(Here an `.luarc.jsonrc` highlighted with neovim as an example)
Otherwise I would have had to try to find out /why the hell/ that works.
(With it I can just look up that part of the grammar in `:h lua-tableconstructor`)
Otherwise I would have had to try to find out /why the hell/ that works.
(With it I can just look up that part of the grammar in `:h lua-tableconstructor`)
I don't know who came up with that, but I wish I could time travel a bit and convince them to be reasonable and NOT allow that.
Luckily `stylua` can just reformat them to `,`s automatically.
I don't know who came up with that, but I wish I could time travel a bit and convince them to be reasonable and NOT allow that.
Luckily `stylua` can just reformat them to `,`s automatically.
"they're deliberately balanced to ensure that code reading isn't made difficult."
We are doing game balancing for programming languages now?!
c3-lang.org
"they're deliberately balanced to ensure that code reading isn't made difficult."
We are doing game balancing for programming languages now?!
c3-lang.org
It sadly doesn't show the full path of the item, but the import statement of the thing being imported, but it should be good enough I guess.
github.com/titaniumtrav...
It sadly doesn't show the full path of the item, but the import statement of the thing being imported, but it should be good enough I guess.
github.com/titaniumtrav...
(Really! I'm 100% sure! It was there just a minute ago!)
(Really! I'm 100% sure! It was there just a minute ago!)
You can't just `move || {}` a Vec into multiple closures.
You can't just `move || {}` a Vec into multiple closures.
I'm pretty sure I have seen it in the past.
Yeah, rust 1.50.0 (2021-02-10) had that feature already.
I'm pretty sure I have seen it in the past.
Yeah, rust 1.50.0 (2021-02-10) had that feature already.
(It is even worse if you learn about it in a different language where the letters are named similarly, but mean different things.)
(It is even worse if you learn about it in a different language where the letters are named similarly, but mean different things.)