Fwd: Using _GLIBCPP_RESOLVE_LIB_DEFECTS in the testsuite?

[Benjamin Kosnik]

>> Sure. I'm implementing a "debug mode" that performs additional 
>> checking of the library usage, and will flag an error (by aborting, 
>> throwing an exception, etc.) when the user invokes undefined behavior 
>> in certain cases. The main component is iterator tracking: extra 
>> information is associated with each iterator that describes, e.g., 
>> what container it references, if it's singular, dereferenceable, or 
>> past-the-end, etc. The library is annotated with assertions that use 
>> this information for additional checks, e.g., that one does not try to 
>> dereference a past-the-end iterator, or compare iterators that are not 
>> in the same domain.

Sounds great!

>> So should we still note when testcases deviate from the standard as is 
>> done in the library?

Yes, this is probably a good idea.

-benjamin