You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
palimondomannequin opened this issue
Feb 17, 2017
· 4 comments
Assignees
Labels
bugA deviation from expected or documented behavior. Also: expected but undesirable behavior.compilerThe Swift compiler in itselfcrashBug: A crash, i.e., an abnormal termination of software
It is however possible to work around this issue and achieve similar result, if instead of using the tuple to store the state, one creates generic struct to hold the same values. See commented code at the end of the attached test case for the implementation of the workaround.
This might be duplicate of SR-3450, though I think that given the workaround with struct works and covers a different use case than using a closure as state directly: I'm trying to store the closure inside a state tuple.
The text was updated successfully, but these errors were encountered:
bugA deviation from expected or documented behavior. Also: expected but undesirable behavior.compilerThe Swift compiler in itselfcrashBug: A crash, i.e., an abnormal termination of software
Attachment: Download
Environment
Xcode Version 8.2.1 (8C1002)
Apple Swift version 3.0.2 (swiftlang-800.0.63 clang-800.0.42.1)
Target: x86_64-apple-macosx10.9
Additional Detail from JIRA
md5: 21011a122103c12274c52bc07e87d5ac
duplicates:
Issue Description:
Compiling this:
crashes the compiler with following error:
It is however possible to work around this issue and achieve similar result, if instead of using the tuple to store the state, one creates generic struct to hold the same values. See commented code at the end of the attached test case for the implementation of the workaround.
This might be duplicate of SR-3450, though I think that given the workaround with struct works and covers a different use case than using a closure as state directly: I'm trying to store the closure inside a state tuple.
The text was updated successfully, but these errors were encountered: