Johel Ernesto Guerrero Peña

It seems you meant R.34-R.36.

That question was brought up in some form at https://github.com/microsoft/GSL. I think the answer was as seen in this comment https://github.com/microsoft/GSL/pull/831#discussion_r359992776, which can be summarized as "setting your own termination...

I mislinked the comment: https://github.com/microsoft/GSL/pull/831#discussion_r359992776. In the original discussion I refer to (which I can't find and is not the linked comment), I remember a recommendation to print the stack...

Also see: https://github.com/microsoft/GSL/pull/900 > The C++ Core Guidelines simply [specify `gsl::narrow`](http://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#gslutil-utilities) as `narrow // narrow(x) is static_cast(x) if static_cast(x) == x or it throws narrowing_error`. The implementation uses relational operators,...

In `finally`, `dismissable` could use a lightweight form of `std::stop_token` to make its call operator a noop. Seems like a good separation of concerns and composition.

Shouldn't that be `int i{0}`?

That seems accidental rather than intentional. The maintainers have expressed their preference for ASCII and rejected "beautiful" double apostrophes in preference of plain "s before, so I believe this change...

This could work: https://godbolt.org/z/q4eTeM6dT. It'd have to be properly integrated with projections. I haven't checked to see if that's possible. Projections already default to `std::identity`, so overloading might be necessary....

> or a language feature to perform overload resolution during template deduction time to bind which overload you want Like https://wg21.link/P1167?

I meant the part titled "Deduction guides for function templates".