gsl not_null throw exception

https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rf-nullptr

Was throwing an exception considered? ie. std::logic_error or std::invalid_argument

Perhaps it is left implementation defined, as I can't spot a specific behavior described.

Presently GSL calls std::terminate(), quite a strong response. gsl-lite is the same.

An exception gives the application a chance to handle it (even if that was just gracefully logging). The user wouldn't be impacted by a std::terminate core dump SEGV; which is a bad outcome in a safety critical environment. Even worse in a library, we can't link to anything that might call std::terminate() like this in a safety critical environment; would be an uncontrolled program termination event.

Here is a one file example based on https://github.com/gsl-lite/gsl-lite

https://godbolt.org/z/Wdea6G9EW

This isn't production code, just an example.

Review the CppCoreGuidelines Rf-nullptr section and the linked Godbolt example, then compare the reported behavior with GSL and gsl-lite. Decide whether not_null exception behavior should be specified, and record the resulting contract; the issue names no repository files or tests.