-
Type:
Improvement
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Internal Code
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
The verify() macro is poorly designed because it throws an exception in release builds, and crashes in debug builds. In practice we can end up hitting verify()s at runtime fairly frequently, as indicated by jstestfuzz.
As part of the 3.3 cycle we should remove the verify macro completely, replacing uses of it with invariant() or uassert() as appropriate.
- duplicates
-
SERVER-6317 Make assertions behave uniformly in debug and normal builds
-
- Backlog
-
- related to
-
-
- Closed
-