Closed swift-ci closed 7 years ago
Unhandled conversion to exploded tuple
UNREACHABLE executed at /Volumes/Data/swift-public/swift/lib/SILGen/SILGenPoly.cpp:962!
1. While emitting SIL for 'f' at <stdin>:1:1
2. While emitting reabstraction thunk in SIL function @_TTRXFo_dSidSi_dSi_XFo_lTSiSi__dSi_
@slavapestov, you've been looking at things like this...
I believe in this case it's actually Sema producing invalid AST, which blows up SILGen.
Oh, yeah, sorry, I didn't mean it was SILGen's fault, just general things around tuples in closures.
Tentatively assigning to @xedin since he's looking at some related issues. Feel free to re-assign π
@slavapestov Thanks! π
Fixed on master with this merge: https://github.com/apple/swift/commit/c04c6c9c61d149b3a46311df770eb70cfaa67bff
Please confirm with a build that has this fix in it and close the issue if you agree the issue is fixed.
Environment
swiftc 3.0.2Additional Detail from JIRA
| | | |------------------|-----------------| |Votes | 0 | |Component/s | Compiler | |Labels | Bug, CompilerCrash | |Assignee | ingoem (JIRA) | |Priority | Medium | md5: 9ecb7420a0cb4bea9dccbd3411386b03is duplicated by:
relates to:
Issue Description:
The following gives a segmentation fault in swiftc:
It compiles when I write an explicit type for the closure or if I pass 0 instead of (0,0) for a0. Now, if I change unfold to use a single type parameter:
instead of giving a type error swiftc just prints
If I change the closure to return (0,0) instead of 0, it segfaults again.