[SERVER-66345] Add a MONGO_UNIMPLEMENTED Created: 10/May/22 Updated: 29/Oct/23 Resolved: 22/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | George Wangensteen | Assignee: | Erin McNulty |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Service Arch 2022-05-30, Service Arch 2022-06-13, Service Arch 2022-06-27 |
| Participants: |
| Description |
|
Right now, our usage of MONGO_UNREACHABLE is somewhat overloaded; we use it to represent both -> "If this code is reached, there is a logic bug" (i.e. default case in an exhaustive switch statement) and -> "It wasn't worth implementing this yet and it shouldn't be reachable from production"
It may be useful to distinguish between the two, especially when reading code. We could add a MONGO_UNIMPLEMENTED to disambiguate. |
| Comments |
| Comment by Githook User [ 23/Jun/22 ] |
|
Author: {'name': 'Erin McNulty', 'email': 'erin.mcnulty@mongodb.com', 'username': 'erin2722'}Message: |
| Comment by Githook User [ 21/Jun/22 ] |
|
Author: {'name': 'Erin McNulty', 'email': 'erin.mcnulty@mongodb.com', 'username': 'erin2722'}Message: |