Why C++ sucks (2016 edition)

Re:Why C++ sucks (2016 edition) by Murk on Monday February 22, 2016 @05:51AM (#11149939)

A lot of people insist on avoiding the use of "using namepspace x" in .cpp files. This makes no sense to me, it makes things a lot easier to read. It never seems to cause a problem, and it's trivially fixed if a conflict shows up due to a header change later.

[ Parent | on HN ]

Re:Why C++ sucks (2016 edition) by jcelerier on Monday February 22, 2016 @05:56AM (#11149952)

> It never seems to cause a problem

It does if you want to use unity builds at some point down the road. For my app it took the build time from 25 minutes to 2 - 3 minutes which is critical when doing CI on a lot of operating systems and with a big build matrix.

[ Parent | on HN ]

Re:Why C++ sucks (2016 edition) by Murk on Monday February 22, 2016 @06:02AM (#11149972)

I am not familiar with unity, but why should it slow down builds?

[ Parent | on HN ]

Re:Why C++ sucks (2016 edition) by lfowles on Tuesday February 23, 2016 @11:55AM (#11160264)

From a quick google, unity builds are akin to #include-ing every file in the project (yes, the .cpp files too).

[ Parent | on HN ]