-
-
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
Crash in protocol conformance code #167
Comments
I'm not so sure it's a SwiftWasm issue now, I've narrowed it down to this line: https://github.com/swiftwasm/Tokamak/blob/b9ade79df1fcf9d9d82d63ec483fcf95faf0840e/Sources/TokamakCore/MountedViews/MountedView.swift#L53 Given that there's some runtime magic that we're doing there, we need to make sure it's applied correctly before we can start assuming it's a SwiftWasm-specific issue. |
UPDATE: Sorry, please disregard that, it could also be a bug in the |
hm, this only happens for the |
BTW, I've just published |
It's not needed there as `ViewBuilder` is smarter now. The macOS SwiftUI SDK even with Xcode 12 still doesn't have the `@ViewBuilder` attribute on the `View` protocol, so we have to build for iOS on CI to make the native buld pass. Resolves #167, which wasn't caused by protocol conformance problems, but by infinite recursion in the `_ConditionalContent` implementation of `body`. Adds assorted formatting fixes, some are apparently caused by the newer `swiftformat` version.
I haven't been able to isolate a minimal test case yet, but this is reproducible in both #130 and #149 with the most recent snapshots in both
swiftwasm
and 5.3 branches, and I tried these snapshots:wasm-5.3-SNAPSHOT-2020-07-07-a
wasm-DEVELOPMENT-SNAPSHOT-2020-07-07-a
wasm-DEVELOPMENT-SNAPSHOT-2020-06-12-a
The stacktrace follows:
The text was updated successfully, but these errors were encountered: