3 ms·

Sure but this is about constexpr, not modules.

• mkoubaa 1y ago
  Modules implicate the entire toolchain, backward compatibility, and binary compatibility. constexpr is a compiler feature. Wild that they are being compared.
  • pjmlp 1y ago
    See how many years it takes for a compiler on average to be 100% compliant after a standard is ratified, not widely at all when one wants to write portable code, regardless.
    • int_19h 1y ago
      In practice it's the same thing with C++ today as it is with web standards: you have to evaluate support on a feature-by-feature basis, and stick to the features that are supported on all the implementations you care about. And constexpr in stdlib is much more likely to get quick adoption across all implementations than something like modules.
      • pjmlp 1y ago
        Not really, folks have done a good job turning the Web into ChromeOS, there is only one relevant browser still standing.
        • int_19h 1y ago
          Safari/WebKit is still very relevant, and it's quite different from Blink even if they have shared origins.
        • mkoubaa 1y ago
          I'll buy this when people who write web pages for a living exclusively support Chrome
• pjmlp 1y ago
  Indeed, however there is a certain velocity how many years after the standard gets ratified until the compilers get fully compliant.