4 ms·
C++ shouldn't be a problem? Just add a new namespace: std::move_fast_and_break_things::vector Or maybe the other way around so you can keep using std::vector:
by properparity 5y ago
C++ shouldn't be a problem? Just add a new namespace:
std::move_fast_and_break_things::vector
Or maybe the other way around so you can keep using std::vector:
move_fast_and_break_things::std::vector
Then you can add a 'using namespace move_fast_and_break_things;' at the top of your files if you know you don't care about the ABI in your program.
- vlovich123 5y agoIn c++ you do this with inline namespaces (change the default inline namespace version, keep the old one around, everything continues to work correctly in theory).
- deleted 5y ago[deleted]
- brandmeyer 5y agoYou can do that with boost:: or absl:: right now. No need to involve the standards committee at all.
- noobermin 5y agoThis doesn't just apply to stl, this also means breaking boost or w/e and you're stuck with the same problem, users are mad and pitted against library writers.
- brandmeyer 5y agoBoost doesn't even have a stable API commitment, let alone a stable ABI. Every release may require involvement from users to keep up to date. Abseil doesn't even have releases any more. They expect you to live at head like GOOG does internally.
- noobermin 5y agoIt's not just new and breaking things, it also applies to fixing bugs.