Sign into an existing account

https://lab.gvid.tv/x0x7/AdventOfCodeSolutions/src/branch/main/2023/Day2

When you care more about getting it done quickly than legibility and you know your functional programming muscle memory a millimeter above good enough to do it in one take.

All the reasons to go header-only are superficial, as is the counter to the compile time problem with thorough templating of every function. This isn't about minor pros and cons, it's about not breaking stuff.

One of the great things about separate declaration and implementation is exactly that, the latter is totally shielded from impact and from impacting anything else. To argue for header-only is to claim that the implementation does not and will never cause any conflict with anything else ever, which is pretentious bullshit.

Sqlite gets it right - they produce amalgamated source, but it's one header file and one source file. The header looks suspiciously large, but that's only because it's 99% comment text to document it.

Some libraries are designed header-only but have a separated version available or a script to produce that, so they get a pass, at least it's not forced header-only.

Then we have shit like Eigen. Nice actual library, but good god damn have they caught the gay header-only HIV. It's just too much time to hit an unexpected compile error for which the resolution involves editing an included library, in this case just to move implementation out of the headers.

For anyone who needs an analogy, the problem with header-only libraries is the same as the problem with open-plan offices.

I'm getting better results generating code from OpenAI. Anybody have a good experience with Copilot?