Skip to content

Conversation

@pvieito
Copy link
Contributor

@pvieito pvieito commented Mar 4, 2018

  • Deprecated old path API as Darwin Foundation

- Deprecated old path API as Darwin Foundation
@alblue
Copy link
Contributor

alblue commented Mar 4, 2018

@swift-ci please test


}

@available(*, deprecated)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are actually not marked as deprecated yet in the SDK.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new implementation looks reasonable but we can leave the deprecation annotation off for now.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is marked as deprecated in the documentation: https://developer.apple.com/documentation/foundation/process/1413110-currentdirectorypath

Maybe it is just an error.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the path API is not deprecated I would prefer to do the inverted implementation (just add the new URL API as an overlay of the path counterparts).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The documentation actually got ahead of us here. It is "soft deprecated", indicating that will eventually be deprecated.

It may seem like splitting hairs but I think we should remain consistent with the annotations in the SDK. Once the SDK marks it deprecated (with a API_DEPRECATED macro, e.g.) then we can add the attribute here.

If you want to invert the implementation, that's fine with me. That's actually how we do it in the ObjC Foundation too.

@pvieito
Copy link
Contributor Author

pvieito commented Mar 6, 2018

Final request: #1462

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