-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[wasm] Gate atomic write option usages behind platform check #5198
base: main
Are you sure you want to change the base?
[wasm] Gate atomic write option usages behind platform check #5198
Conversation
@swift-ci test |
I've forgotten to change swift-corelibs-foundation. Thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are people using the NSData
class on WASI, instead of the Data
struct?
Yes, there are still certain amounts of existing code using that running on the platform. |
@swift-ci test Windows |
I have the same general concern here, that we're simply suppressing the error instead of doing something to tell the developer it won't work. I wonder if it would be better to make the whole method unavailable. |
`Data.WritingOptions.atomic` is now unavailable on WASI: swiftlang/swift-foundation#992
ac84026
to
37f6d25
Compare
@parkera Good point. I think it makes sense to make them unavailable on WASI. |
@swift-ci test |
@swift-ci test Windows |
Data.WritingOptions.atomic
is now unavailable on WASI swiftlang/swift-foundation#992, so we need to gate them behind platform checks