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
Attempting to build BlueSignals on Linux (or a project which depends on it - such as Kitura) with the latest Swift 5.1 snapshot (swift-5.1-DEVELOPMENT-SNAPSHOT-2019-04-17-a) fails with:
This seems to relate to the @escaping attribute, and the various trap() function signatures. Specifically, there is one function that takes an array of (Signal,SigActionHandler) tuples, where the SigActionHandler is not explicitly marked as @escaping, however this is then passed to another trap() function where it is escaping.
I couldn't find a syntax that allows you to mark the SigActionHandler that is embedded in the tuple type as escaping, and to be honest I'm not sure how this currently compiles - the fact that it blows up (rather than producing a proper error) on 5.1 suggests it might be a compiler issue, but I'm not really sure.
The text was updated successfully, but these errors were encountered:
I don't think this is a problem (except maybe with the compiler). Early in Swift 4.2 snapshot cycle, I had virtually the same thing happen to me. The compiler would dump on that particular function. Since it was a compiler crash rather than an error, I reported it to Apple using the BlueSignals project as an example. They fixed it rather quickly. I'd say watch it and see if it continues to crash with subsequent snapshots and if so, file another bug report.
Attempting to build BlueSignals on Linux (or a project which depends on it - such as Kitura) with the latest Swift 5.1 snapshot (
swift-5.1-DEVELOPMENT-SNAPSHOT-2019-04-17-a
) fails with:This seems to relate to the
@escaping
attribute, and the varioustrap()
function signatures. Specifically, there is one function that takes an array of (Signal,SigActionHandler) tuples, where the SigActionHandler is not explicitly marked as@escaping
, however this is then passed to anothertrap()
function where it is escaping.I couldn't find a syntax that allows you to mark the SigActionHandler that is embedded in the tuple type as escaping, and to be honest I'm not sure how this currently compiles - the fact that it blows up (rather than producing a proper error) on 5.1 suggests it might be a compiler issue, but I'm not really sure.
The text was updated successfully, but these errors were encountered: