3 ms·

This detail is just one part of the library's broader disregard for the scope of names. One of the most difficult parts of managing large projects is dividing

This detail is just one part of the library's broader disregard for the scope of names. One of the most difficult parts of managing large projects is dividing up the global namespace in a way that is equitable to all authors. This library has a number of naming problems: It claims names that are reserved for the compiler and runtime libraries. It puts names into the global namespace. Worse, it puts generic names like "parser" and "store" into the global namespace. It also claims an extremely broad category as its own project name (Serialization++? Seriously?). It doesn't matter how clever your particular library is. In total, the impact of those naming problems makes your library disrespectful to the broader C++ community.

apankrat 7y ago
Get off your high horse and step away from the espresso machine. Readme> It's not meant to be an universal serialization library, but rather a real-life working example of one of many ways to do serialization. It's an extract from the existing code base. It is TRIVIAL to put the whole thing into a separate namespace. It's TRIVIAL to change the names if they really rub you the wrong way. The point of this repo is to show a _technique_ for doing serialization, and yet here you are fuming and nitpicking on petty details. > Disrepectful to the broader C++ community This is so ridiculous I'm not sure how this anything but trolling.