[SERVER-35683] Make it safe to destroy a promise while it's being completed Created: 19/Jun/18 Updated: 29/Oct/23 Resolved: 26/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.2 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | ADAM Martin (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Platforms 2018-07-16, Platforms 2018-07-30 |
| Participants: |
| Description |
|
It is a common pattern that we make a promise which on its fulfillment causes the destruction of the promise. We should make that safe |
| Comments |
| Comment by Githook User [ 26/Jul/18 ] |
|
Author: {'username': 'adamlsd', 'name': 'ADAM David Alan Martin', 'email': 'adam.martin@10gen.com'}Message: Moving the shared-state pointer for the future out of the promise, |
| Comment by Githook User [ 26/Jul/18 ] |
|
Author: {'username': 'adamlsd', 'name': 'ADAM David Alan Martin', 'email': 'adam.martin@10gen.com'}Message: Some members of classes in the `Future` family of types were not |
| Comment by Mathias Stearn [ 19/Jun/18 ] |
|
While you're in there, please fix Promise's members to use the _normalNamingConvention. |