-
Notifications
You must be signed in to change notification settings - Fork 112
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
[Swift 5.1] Import FoundationXML rather than Foundation #121
Comments
As far as I understand, the recommended way is to use #if canImport(FoundationXML)
import FoundationXML
#endif Probably can even be included before 5.1 release. |
5.1 was released. Can submit PR. Need it for production use of this library. |
@mxcl very excited to see this library in production! Please let me know if that's public, I'd be happy to feature it in the README file. 5.1 support for Linux is in |
Use is private currently, will advise when we're more public! Thanks for the lib, was essential for our backend services. |
@MaxDesiatov, looks like you took care of this in #133! Want me to close this down, or is there anything else that needs to be done? |
@jsbean, thanks for checking! I'll keep this open until 0.9 is formally released, primarily as a reminder for this to be added to the CHANGELOG file etc. |
Closing as fixed in the imminent 0.9 release. |
As of this PR onto the Swift 5.1 branch,
XMLParser
lives in a split-offFoundationXML
framework rather thanFoundation
.Once Swift 5.1 drops, perhaps we check against the compiler version to import accordingly?
This is a reality as of DEVELOPMENT-SNAPSHOT-2019-08-03-a.
The text was updated successfully, but these errors were encountered: