[SERVER-29911] Use shared_ptr in Restriction sets instead of unique_ptr Created: 28/Jun/17  Updated: 30/Oct/23  Resolved: 30/Jun/17

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 3.5.10

Type: Task Priority: Major - P3
Reporter: Sara Golemon Assignee: Sara Golemon
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Minor Change
Sprint: Platforms 2017-07-10
Participants:

 Description   

The way we actually want to use Restriction sets in the RolesGraph and on User objects means that we potentially want to create many common references to the same authenticationRestrictions and their cross-products.

This means either making them sharable, or at the very least copyable. Let's go for shared_ptrs and simplify our lives.



 Comments   
Comment by Githook User [ 30/Jun/17 ]

Author:

{u'username': u'sgolemon', u'name': u'Sara Golemon', u'email': u'sara.golemon@mongodb.com'}

Message: SERVER-29911 Use shared_ptr for Restriction sets
Branch: master
https://github.com/mongodb/mongo/commit/acc6b704793fc37d5439b32b64a186a500436a36

Generated at Thu Feb 08 04:22:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.