3 ms·
> very minimal/low-feature language, that’s fairly low level, even if that means somewhat more awkward or mistake-prone code Do you think this is a good trade-
by adwn 5y ago
> very minimal/low-feature language, that’s fairly low level, even if that means somewhat more awkward or mistake-prone code
Do you think this is a good trade-off?
If you're using a tool every day or at least regularly, the one-time cost of mastering a slightly more complex tool is amortized over all uses of that tool.
- rob74 5y agoYou may be using the tool every day, but are you using this "disable field reordering" annotation every day? Also, after you used it, you may remember what "#[repr(C)]" does, but I bet most of the other developers working with the code in the future will have to look it up (unless you leave a comment). So the trade-off is not as cheap as you think...
- adwn 5y ago
- yashap 5y agoI didn’t pass any judgement on whether it’s a good or bad tradeoff, just that it’s in-line with Go’s general approach to language design.