Get the latest tech news
C++: "model of the hardware" vs. "model of the compiler" (2018)
Quote:"we MUST NOT care about compiler internals beyond our task definition (which is based on (a) humans, and (b) hardware, that's it)."Another Quote:"My problem with introducing a 'model of the compiler' into the picture, is that it can be used to justify pretty much anything without any relation to real-world requirements."[→]
Author: “No Bugs” Hare Follow: Job Title: Sarcastic Architect Hobbies: Thinking Aloud, Arguing with Managers, Annoying HRs, Calling a Spade a Spade, Keeping Tongue in Cheek Recently, I have run into[P1063R0], and was literally stunned with a way those guys (mis)interpret certain fundamental aspects of C++ philosophy. For example, C++ templates provide a direct and efficient map of the compiler’s code generation facilities, rather than of any hardware feature”. But the problem I see with introducing implementation details of the compiler into the philosophy is much more general than that – it can be used to justify pretty much anything, and IMNSHO that’s where the real danger to the language lies.
Or read this on Hacker News
