We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
10.14 (18A391)
Xcode Version 10.0 (10A255)
md5: 76b5dc2ad471196ee7a293da3a60672a
duplicates:
Issue Description:
It seems that using lazy.map leads to a Swift demangling issue:
SWIFT RUNTIME BUG: unable to demangle type of field '_transform'. mangled type name is 'q_7ElementSTQzc'
Paste into a Playground:
let l = [1, 2, 3, 4, 5] let a = l.lazy.map { i -> Int in return i } l
Using l.map instead of l.lazy.map alleviates the error.
The text was updated successfully, but these errors were encountered:
Funny you should mention this, as I just logged on in order to report SR-9058 which also emits the same kind of error message.
Sorry, something went wrong.
Comment by Daniel Jalkut (JIRA)
Ah yes! Funny timing. Seems like they must be related.
And swiftly being duplicated against SR 8354!
No branches or pull requests
Environment
10.14 (18A391)
Xcode Version 10.0 (10A255)
Additional Detail from JIRA
md5: 76b5dc2ad471196ee7a293da3a60672a
duplicates:
Issue Description:
It seems that using lazy.map leads to a Swift demangling issue:
SWIFT RUNTIME BUG: unable to demangle type of field '_transform'. mangled type name is 'q_7ElementSTQzc'
Paste into a Playground:
Using l.map instead of l.lazy.map alleviates the error.
The text was updated successfully, but these errors were encountered: