[SERVER-77960] MultikeynessTrie fails to compile when kContainerImpl = STD Created: 09/Jun/23  Updated: 29/Oct/23  Resolved: 23/Jun/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: David Percy Assignee: Maya Srikanth (Inactive)
Resolution: Fixed Votes: 0
Labels: bonsai-onboarding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: QO 2023-06-12, QO 2023-06-26
Participants:

 Description   

Currently, MultikeynessTrie uses opt::unordered_map, which is an alias for either std::unordered_map or stdx::unordered_map depending on a compile-time flag (kContainerImpl). One of these is failing to compile. The problem is that the map contains MultikeynessTrie by value: some but not all map types support this, because they use some pointer / indirection internally.

Let's make sure MultikeynessTrie compiles regardless of the value of kContainerImpl. One way is to have MultikeynessTrie use std::map directly instead of opt::unordered_map.



 Comments   
Comment by Githook User [ 13/Jun/23 ]

Author:

{'name': 'Maya Srikanth', 'email': 'maya.srikanth@mongodb.com', 'username': ''}

Message: SERVER-77960 unordered_map -> map
Branch: master
https://github.com/mongodb/mongo/commit/2b2432766552d783eae2eb23f5efafb9047492a6

Generated at Thu Feb 08 06:37:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.