The whole point of the complexity chrono interface is to prevent mistakes caused by accidentally mixing different units. Providing a default unsafe interface would completely defeat the point.

That an interesting point of view to take in defence of C++ of all things.

Sorry, I might misparsing your replay, but are you saying that std::chrono is overly strict? Or that because C++ (and its C heritage) has allowed unsafe implicit conversions in the past, it should continue doing it in the future?

Just that it feels strange to see safe defaults/interfaces used to argue for C++, nothing more.