Skip to content

Adding get_mut/get_key_value_mut for both RangeInclusiveMap and RangeMap#111

Open
noctice007 wants to merge 1 commit intojeffparsons:mainfrom
noctice007:adding_mutablility
Open

Adding get_mut/get_key_value_mut for both RangeInclusiveMap and RangeMap#111
noctice007 wants to merge 1 commit intojeffparsons:mainfrom
noctice007:adding_mutablility

Conversation

@noctice007
Copy link

No description provided.

@jeffparsons
Copy link
Owner

Thanks for the pull request.

I'm open to having these methods, but I'd want them to ensure that adjacent ranges mapping to the same value are coalesced after any change is made. (Currently all other mutating methods uphold this guarantee.) This might be a tad inefficient with the BTreeMap APIs available today, but it looks like extract_if is about to be stabilised, and that might help? I'd be fine with gating new methods on having a new enough compiler, if required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants