Just saying...
:%s/\s*—(\s*)/, /g
Just saying...
:%s/\s*—(\s*)/, /g
Yes, but the tools provided by Rust:
unsafe {} block to be used.the GPL has become so complicated that only a programmer with relatively advanced legal knowledge and ability to read and properly understand “legalese” will be able to decipher it to know what they are able and unable to do with it
I have read the GPL and it is not very complicated. It's long so you need an attention span to understand it but it's written in reasonably plain language and doesn't contain excessive references. It even goes so far as to provide a summary at the beginning.
...which is why I love #[rustfmt::skip] so much! You can do stuff like
#[rustfmt::skip]
const DIRECTIONS: [[i8; 2]; 4] = [
[0, 1],
[-1, 0], [1, 0],
[0, -1],
]
while still enjoying the convenience of auto formatting elsewhere.
Although linters which act on the behavior of code are unequivocally a good thing, e.g. "hey, this comparison will always return false you probably made a mistake here".
People (such as myself) make the argument that it does a better job because it's focused more on reading code than writing it since you don't start in the "write" mode like in most editors.
I would say the choice of text editor shouldn't make a difference in productivity so long as it doesn't actively get in your way too often (looking at you, poorly implemented autopairs) and it supports the relevant LSP and debugging protocols.
Regardless of whether this is fake, it feels like this is the weirdest thing I've ever read on the internet.
It is FOSS, see other comments.
They do. Mindustry, Residual, and Asperite come to mind.
Mindustry seems to be doing just fine.
Yes, but:
