IPath.WithExtension: behavior and documentation improvements - #230
Merged
Merged
Conversation
ForNeVeR
force-pushed
the
bugfix/153.weird-extensions
branch
from
October 4, 2026 18:29
32bf08b to
b7a88fb
Compare
ForNeVeR
force-pushed
the
bugfix/153.weird-extensions
branch
from
October 4, 2026 18:38
1dbf364 to
f1b5f3a
Compare
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.
I have found some dubious use cases for the
.WithExtensionand decided to exterminate them.The new contract is that it will never change the path segment count (never introduce a new entry or destroy an existing one), and it won't change the last path segment type (won't convert root to anything else, parent/current folder reference to anything else).