3 ms·
But with any complex interface, wouldn't it be a good idea to introduce a less complex facade that only deals with common usecases, and for complex use cases us
by chris_wot 11y ago
But with any complex interface, wouldn't it be a good idea to introduce a less complex facade that only deals with common usecases, and for complex use cases use that underlying interface?
- gpderetta 11y agoThe 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.
- masklinn 11y agoThat an interesting point of view to take in defence of C++ of all things.
- gpderetta 11y agoSorry, 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?
- masklinn 11y agoJust that it feels strange to see safe defaults/interfaces used to argue for C++, nothing more.