Remove TryInsertResult::Empty#3103
Open
Huliiiiii wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This fixes a legacy semantic issue. In practice, the
Emptybranch is usually unreachable because empty inputs are already handled byInsertMany, so removing it makes the semantics clearer.At this point,
TryInsertResultis effectively equivalent toOption, so it could be further simplified to useOptioninstead of a custom type. Users can still reproduce the previousTryInsert::Conflictsemantics with their owninput.is_empty()andlast_insert_id.is_none()checks when needed.The changelog needs to be updated to explain the corresponding behavioral changes.
Breaking Changes
TryInsertResult::Empty