John McFarlane

I am currently stuck on GSL 2.x because 3.0 violates the zero-overhead principle and does not cater for high-performance applications. A contract violation should not happen in bug free code....

@shaneasd > When you say the user are you referring to the end user of the software or the user of a library? The library user. > I guess in...

@elshize @daviddetweiler a guiding design principle behind C++ is that no programmer should pay (in terms of run-time cost) for a feature that they do not use. When used correctly,...

@daviddetweiler firstly we should agree that we're focussing on bugs here: run-time conditions which absolutely cannot occur in correct code and for which the appropriate course of action is to...

That would be fine except that is means that `gsl::span` is no longer suitable for some safety-critical and performance-critical applications. That in turn would also be fine except the CCG...

I do feel that `GSL_UNENFORCED_ON_CONTRACT_VIOLATION` should have been retained as a mode for `Expects`. It's one of the "alternatives to terminate" which works really well under a UB sanitizer.

@MikeGitb ... which it did with `GSL_UNENFORCED_ON_CONTRACT_VIOLATION` up until this recent policy change. Now we get occasionally slower performance-critical code and analysis tools which are a little less able to...

After removing the `, breathe.file_state_cache.MTimeError: Cannot find file: /home/john/ws/revision/generate/xml/cpp/types/add_cv.xml This is caused by a tag file which pulls in a large number of references to external pages. Here is [the...

Hi @josmithiii. Which tests do you mean? Unfortunately yes, there isn't currently a package available in a public package repo. This issue tracks plans to remedy that in Conan Center....

Please give me a few days to look into this. I'm currently en route to CppOnSea and don't have a lot of bandwidth right now.