On Built Module Interface Compatibility - vito.nyc
Discussing the problem of built module interface compatibility in C++ build systems, and testing which popular build systems do and do not support BMI compatibility calculation.
Domain expertise is a funny thing. Before developing some expertise in a domain, we often judge tools from that domain based on their ease-of-use. Think of the controls of a consumer road car compared to a Formula One race car. The consumer car is "better" because it's intuitive to use, teenagers get the hang of it in a few weeks. If all you need is to commute from one place to another, these controls and the machine they're attached to are perfectly servicable. However, once domain expertise has been established, we often stop thinking in terms of ease-of-use and begin thinking in terms of ca
saved by
related reading
- Cognitive load is what mattersminds.md
- Computers can be understood - Made of Bugsblog.nelhage.com
- A friendly introduction to machine learning compilers and optimizershuyenchip.com
- GitHub - BuildIt-lang/buildit: Online demo without installing at - https://buildit.so/tryitgithub.com
- build-systems-a-la-carte-theory-and-practice.pdfcambridge.org
- Signals and Threads | Build Systemssignalsandthreads.com
- Struct padding in C++ - Stack Overflowstackoverflow.com
- Extensible Extension Mechanismsmarijnhaverbeke.nl
- Effortless Performance Improvements in C++ | Julien Jorge's Personal Websitejulien.jorge.st
- Before you try to do something, make sure you can do nothingdevblogs.microsoft.com
- Prompts are code, .json/.md files are statemariozechner.at
- There's no reason for software to be slow anymoredanluu.com