3 ms·

That’s a find-and-replace fix that can be addressed reliably. A relatively smaller problem versus moving off of boost. The compiler support for C++11 (and esp

• Jasper_ 7y ago
  Right, moving to std::cout to fmt could be as simple as a find-and-replace fix. That the C++ committee could have inflicted this minimal pain on their users, but chose not to do it, shows some amount of concern for backwards compatibility and old codebases. By comparison, Python 3 changed the entire text model and dropped the mic, and waited for 8 years to start to pick the pieces back up.
  • choppaface 7y ago
    I guess I don’t understand your argument that “Python 3 changed the entire text model and dropped the mic.” format strings are optional; the old % operator still works fine. The change to unicode is dramatic, but personally I haven’t run into major problems. I’ve had unit tests break because of it, but that’s why one has unit tests. I’ve also worked on a very large python webapp that underwent painful internationalization, and in that case we ended up using unicode strings everywhere anyways.
    • richardwhiuk 7y ago
      The % didn't use to work fine. .iteritems() was made for no good reason. Python 3 could have required all strings began with u" or b", but they didn't - they did something which encouraged breakage.