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 software
The compiler warnings are expected: the assert is not. Removing the -emit-module-path test.swiftmodule prevents the crash, so this suggests that the issue is specifically due to having a module context.
I've only reproduced this on Linux: running equivalent code on macOS does not hit the same crash.
The text was updated successfully, but these errors were encountered:
I've talked to @DougGregor about this and it looks like we'd want to ban generic typealias spelling without generic parameters specified but it only currently broken when underlying type is a typealias as well, temporarily I'm going to allow their serialization again but we'll need to figure out more comprehensive solution for long term.
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
Environment
Ubuntu 16.04
Swift version 4.1-dev (LLVM 7598a1fc69, Clang 8be462d5b8, Swift 4e7b4de)
Target: x86_64-unknown-linux-gnu
Additional Detail from JIRA
md5: 43f48fce709961242ed4944319ac008e
is duplicated by:
Issue Description:
Using the following sample "module" on Linux will crash the Swift 4.1 development compiler. If you save the following to a file called
test.swift
:And run the following compiler invocation with a recent 4.1 snapshot compiler on Linux:
then the compiler will crash with the following output:
The compiler warnings are expected: the assert is not. Removing the
-emit-module-path test.swiftmodule
prevents the crash, so this suggests that the issue is specifically due to having a module context.I've only reproduced this on Linux: running equivalent code on macOS does not hit the same crash.
The text was updated successfully, but these errors were encountered: