Add more back/front methods and deprecate unspecified inserts #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For
RingMapandRingSet, this just deprecatesinsert_fullin favor of the existingpush_backandpush_front. The plaininsertmethod is left as-is, as a sort of "I don't really care about order" method that doesn't return an index, but it also documents to see the explicit push methods.For
Entrytypes, I've added a bunch of back/front methods and deprecated all the insert-like originals.insert=>push_back,push_frontinsert_entry=>push_back_entry,push_front_entryor_default=>or_push_back_default,or_push_front_defaultor_insert=>or_push_back,or_push_frontor_insert_with=>or_push_back_with,or_push_front_withor_insert_with_key=>or_push_back_with_key,or_push_front_with_keyFixes #10.