This is not an issue per se but from viewpoint of the users who disabled _ITERATOR_DEBUG_LEVEL in debug due to the way it affects parallel performance, more lightweight _CONTAINER_DEBUG_LEVEL seems to be very useful, providing just simple bounds checking etc. However I see that it's not documented as well as _ITERATOR_DEBUG_LEVEL and I wonder if defining it is a public, official feature and thus it's okay to use it or is it for internal use only? Also it'd be nice to see the scope of checks enabling it performs without looking at sources of course.
Feel free to close if I should create an issue somewhere like in https://github.com/MicrosoftDocs/cpp-docs about this instead.
This is not an issue per se but from viewpoint of the users who disabled
_ITERATOR_DEBUG_LEVELin debug due to the way it affects parallel performance, more lightweight_CONTAINER_DEBUG_LEVELseems to be very useful, providing just simple bounds checking etc. However I see that it's not documented as well as _ITERATOR_DEBUG_LEVEL and I wonder if defining it is a public, official feature and thus it's okay to use it or is it for internal use only? Also it'd be nice to see the scope of checks enabling it performs without looking at sources of course.Feel free to close if I should create an issue somewhere like in https://github.com/MicrosoftDocs/cpp-docs about this instead.