Skip to content
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

Update AnyView status in progress.md #151

Merged
merged 1 commit into from
Jul 2, 2020
Merged

Update AnyView status in progress.md #151

merged 1 commit into from
Jul 2, 2020

Conversation

MaxDesiatov
Copy link
Collaborator

@MaxDesiatov MaxDesiatov commented Jul 2, 2020

IDK, is there anything that SwiftUI AnyView can do that ours can't? ¯\_(ツ)_/¯

IDK, is there something that SwiftUI `AnyView` can do that ours can't? ¯\_(ツ)_/¯
@MaxDesiatov MaxDesiatov added the SwiftUI compatibility Tokamak API differences with SwiftUI label Jul 2, 2020
@MaxDesiatov MaxDesiatov requested review from carson-katri and j-f1 July 2, 2020 20:29
@j-f1
Copy link
Member

j-f1 commented Jul 2, 2020

There’s AnyView(erasing: View). I’m not sure if it’s actually behaviorally different but if not it should be an easy add.

@MaxDesiatov
Copy link
Collaborator Author

I think the erasing initializer is some kind of under the hood bugfix, it's marked as @_alwaysEmitIntoClient, the rest of the initializers are underscored.

For context:

@_alwaysEmitIntoClient is useful for keeping a particular declaration out of the ABI.

@MaxDesiatov MaxDesiatov merged commit afba02d into main Jul 2, 2020
@MaxDesiatov MaxDesiatov deleted the anyview-status branch July 2, 2020 22:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
SwiftUI compatibility Tokamak API differences with SwiftUI
Development

Successfully merging this pull request may close these issues.

3 participants