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-6557] init case of enum can be used implicitly #49107

Closed
mbrandonw opened this issue Dec 7, 2017 · 2 comments
Closed

[SR-6557] init case of enum can be used implicitly #49107

mbrandonw opened this issue Dec 7, 2017 · 2 comments
Assignees
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. compiler The Swift compiler in itself

Comments

@mbrandonw
Copy link
Contributor

Previous ID SR-6557
Radar rdar://35852727
Original Reporter @mbrandonw
Type Bug
Status Resolved
Resolution Done
Additional Detail from JIRA
Votes 0
Component/s Compiler
Labels Bug
Assignee @slavapestov
Priority Medium

md5: 324fdae779938133f473ce7d3b42961e

relates to:

  • SR-1660 Enum with String rawValue and escaped init identifier causes compile error

Issue Description:

If you have an `init` case of an enum, you can use it implicitly just like you can with structs:

enum Foo {
  case `init`(Int)
}

// I would expect this to work...
let bar = Foo.init(1)

// ...but not this
let foo = Foo(1)

Is that intentional?

@belkadan
Copy link
Contributor

belkadan commented Dec 8, 2017

Definitely a bug. This is caused by init not having a special DeclBaseName yet, like subscripts and deinits.

@slavapestov, you just got a Radar for this, right?

@slavapestov
Copy link
Member

#15201

@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
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. compiler The Swift compiler in itself
Projects
None yet
Development

No branches or pull requests

3 participants