Skip to content

un-deprecate AbsolutePath::appending(RelativePath) #341

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 13, 2022

Conversation

tomerd
Copy link
Contributor

@tomerd tomerd commented Jul 13, 2022

motivation: concatinating rlative path to absolute path is a key API we should preserve it, but improve the implementation

chnages: remove deprecation marker from AbsolutePath::appending(RelativePath)

work to improve the implementation is tracked in #336

motivation: concatinating rlative path to absolute path is a key API we should preserve it, but improve the implementation

chnages: remove deprecation marker from AbsolutePath::appending(RelativePath)

work to improve the implementation is tracked in swiftlang#336
@tomerd
Copy link
Contributor Author

tomerd commented Jul 13, 2022

@swift-ci test

@tomerd tomerd merged commit 82d7209 into swiftlang:main Jul 13, 2022
tomerd added a commit to tomerd/swift-tools-support-core that referenced this pull request Jul 13, 2022
motivation: concatinating rlative path to absolute path is a key API we should preserve it, but improve the implementation

chnages: remove deprecation marker from AbsolutePath::appending(RelativePath)

work to improve the implementation is tracked in swiftlang#336
@compnerd
Copy link
Member

I thought that the plan was to undeprecate on 5.7 only and change the interface on main?

tomerd added a commit that referenced this pull request Jul 13, 2022
motivation: concatinating rlative path to absolute path is a key API we should preserve it, but improve the implementation

chnages: remove deprecation marker from AbsolutePath::appending(RelativePath)

work to improve the implementation is tracked in #336
@tomerd
Copy link
Contributor Author

tomerd commented Jul 13, 2022

@compnerd we prefer not to diverge across main and 5.7 that way, and would like to work on #336 immediately to get main to the desired state. the first step is #343, which we will follow up with a fix for #336 (slacked you separately about that)

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.

3 participants