4 ms·
It's a substantial quality of life improvement to be able to express things like: vv = 3f_add(&v, &(3f_t){.x = .1, .y = .2, .z = .3 }); vs. having to declar
by pengaru 3y ago
It's a substantial quality of life improvement to be able to express things like:
vv = 3f_add(&v, &(3f_t){.x = .1, .y = .2, .z = .3 });
vs. having to declare and name the literal 3f_t beforehand, wasting my time and cluttering up the code with noise.
- thesnide 3y agoI actually was also thinking that way. But then, after looking back at my old code, I struggled and crafted my 1SLOC guiding principle. I never looked back. Wasting time when writing code is actually an investment into future read speed. I even wrote some time ago about my rationale for 1SLOC https://blog.pwkf.org/2022/09/18/always-optimize-for-dummies.html https://blog.pwkf.org/2022/09/18/always-optimize-for-dummies...
- seba_dos1 3y agoI agree with the principle, but I don't agree that this is where it applies. Initializing things separately just makes it easier to make mistakes that are difficult to spot and harder for compiler to come up with meaningful warnings. It also doesn't make it immediately obvious to the reader that it's just a value to be passed as argument rather than further operated on.