Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SR-5691] Compiler fails badly if default value is computed property of an enum value #48261

swift-ci opened this issue Aug 15, 2017 · 1 comment


Copy link

@swift-ci swift-ci commented Aug 15, 2017

Previous ID SR-5691
Radar None
Original Reporter Reitzig (JIRA User)
Type Bug
Status Resolved
Resolution Duplicate

XCode 8.3.3 (8E300fb) (via AppCode)
Apple Swift version 3.1 (swiftlang-802.0.53 clang-802.0.42)
Target: x86_64-apple-macosx10.9

XCode 8.3 (8E162) (directly in XCode)
Apple Swift version 3.1 (swiftlang-802.0.48 clang-802.0.38)
Target: x86_64-apple-macosx10.9

(Apparently I have two installations, AppCode using one of them. Oh well.)

Additional Detail from JIRA
Votes 0
Component/s Compiler
Labels Bug, CompilerCrash
Assignee None
Priority Medium

md5: 1a7d653a93073c11da4394b556dd25bb


  • SR-2189 Nested function with local default value crashes

Issue Description:

Consider this code:

enum Foo {
    case a

    var d: String {
        return "foo"

func bar() {
    let a = Foo.a

    func foo(b: String = a.d) -> String {
        return "Foo: \(b)"


Expected: Compiles, at least as long as the compiler can figure out that a.d is a constant; otherwise, compilation fails with a meaningful error message.

Actual: "Error: /.../swiftc failed with exit code 1"

Copy link
Collaborator Author

@swift-ci swift-ci commented Aug 15, 2017

Comment by Raphael (JIRA)

Side note: is there a place where I can vent frustration in a completely unconstructive manner? Bugs like this one keep wasting my time. Finding the cause of sudden "exit code 1" failures takes ages, and boiling them down to MWEs even longer.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant