10

I swear to god "old school" C++ devs are menace to humanity

Why yes let's make this one line long function, that could even be constexpr, and make it a macro.
Why the fuck not, let's make compiler errors worse by foregoing any type checking. Let's throw away namespacing as well, great.

Fuck you.
I shouldn't have to dig through 4 levels of nested macros just cause "muh performance" and "we've always done it like that".
Shit yourself.

Comments
  • 5
    You need to accept that the compiler and optimizer are smarter than you are.

    Let them optimize it. Constexpr even implies inline, yon can leave out the inline keyword too
  • 1
    I am waiting to the official release of Carbon.

    It should be the typescript version of C++ :D
  • 3
    @Grumm found the JS dev!
  • 0
    @atheist preach it
    I'm very much in the camp of "if its worth to inline, the compiler/optimizer will do it for me"
  • 0
    @atheist declarations in multiple compilation units being OK, isn't that more like static?
  • 0
    @sariel haha, not really a JS dev here.

    90% of my job is in C#
Add Comment