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
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 softwareIRGenLLVM IR generationSILGenArea → compiler: The SIL generation stage
Might be fallout from @rjmccall's change to lower Optional parameter types. If we aren't holding on to the formal function type Optional<(T...) -> U>, we wouldn't be able to form the metadata for an unspecialized generic Optional operation like this.
Maybe. It looks to me like we're emitting the generic arguments to a function, though, implying that there's a substitution using a SILFunctionType as the argument. Maybe there's something in SILGen that's harvesting substitutions from the SILType of the base instead of taking them from the ConcreteDeclRef.
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 softwareIRGenLLVM IR generationSILGenArea → compiler: The SIL generation stage
Attachment: Download
Environment
Fedora 24 & macOS
Additional Detail from JIRA
md5: d2c43862690a34c95ec8f68d07a17d71
Issue Description:
Fresh master build from 10/21/2016.
Test case:
The text was updated successfully, but these errors were encountered: