security profile that disallows any functions that might throw exceptions in the constructor?

[shemeshg]

This approach could significantly reduce potential vulnerabilities and improve the overall stability of our code. After all, we already have noexcept specifier .

This is important because exceptions thrown in the constructor are not caught or recoverable.

[gregmarr]

@shemeshg Why do you think that constructor exceptions are not catchable or recoverable? Do you mean the destructor, which is noexcept by default?

[shemeshg]

It was my experience with Qt, perhaps because it is signal and slot driven, that having a potential exception thrown from another thread in the constructor without emit is just ignored.

Let me do some tests and I will post the results here for standard C++ as well. I'll post what I find here.

[shemeshg]

Wow, my bad. It is totally a Qt-specific issue and a result of the specific signal-slot mechanism in Qt.

Thanks for enlightening me on this point.

(yet, I don't recommend exception in cont'r/destructor as a practice)

[gregmarr]

Glad you figured out the issue.