Hi,
Again, only if the damn ISO standard required compilers to refuse to compile functions which could throw exceptions inside a noexcept execution context ...
I disagree here. In many applications I would consider functions noexcept even when they can, in theory, throw. Best example is "out of memory" aka "pc lit on fire". Exception handling of rare exceptions is probably among the least tested control paths, so I would often rather terminate in the case of an "unexpected exception" than go on and gamble whether my exception handling is going to die trying to overwrite my last good program state on disk. Therefore, compiler noise like that would probably lead to random try{...}catch(...){} inside all noexcept functions rather quickly. Best, Oswin