Gabriel Dos Reis

It is the express design and intent of `gsl::span` to provide bound safety by fast failing on out-of-bound access. For cases where people want a different behavior -- e.g. blissfully...

@apenn-msft > [...] the author applying the guidance cannot reason about the future location and relativity of where their code is installed In fact, reasoning about where the library/header is...

@apenn-msft > @gdr-at-ms "include search path" is ambiguous; 19.2.2 and 19.2.3 both refer to a "search" being conducted for both and "" forms. I think the term could work if...

That rule should define 'consume', 'forward', 'in', 'out'. Then for each of the following rules, there should be a clarifying note referring back to that rule.

General point taken. On this specific example: > `constexpr int c_specialValue = 42; // even better, visualizes global scope` I wouldn't recommend it as "even better".

This is meant to apply to 'const' local statics -- not general local statics. A dynamic initialization incur some overhead (since it has to be guarded by a mutex of...

Well, it is not really an alternative if the data is intended to be non-modifiable. Some non-const local statics have their uses as singleton, but that is not the subject...

If you can't make the function constexpr so that you get a compile-time constant, you have an exception on your hands. But, that is not the focus of this issue....

Note that overtime, GSL implementations will be removed in favor of the standard library implementations (when the corresponding specs are adopted).

VS 2013 does not support `constexpr` and `noexcept`, not to the extent that we would like to provide much better experience. We don't expect that support to last for a...