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

Jump to bottom

[SR-9779] Crash while emitting SIL for curried call to protocol instance method #52205

Closed
AnthonyLatsis opened this issue Jan 28, 2019 · 0 comments
Closed

[SR-9779] Crash while emitting SIL for curried call to protocol instance method #52205

AnthonyLatsis opened this issue Jan 28, 2019 · 0 comments
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. compiler The Swift compiler in itself crash Bug: A crash, i.e., an abnormal termination of software

Comments

@AnthonyLatsis
Copy link
Collaborator

Previous ID SR-9779
Radar None
Original Reporter @AnthonyLatsis
Type Bug
Status Resolved
Resolution Duplicate
Environment

Version 10.1 (10B61), late December master

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

md5: 1989b93ce2f7e571b4362742e3c15cc9

duplicates:

  • SR-75 Referencing a protocol function crashes the compiler

Issue Description:

protocol P {
  func foo()
}
class A: P {
  func foo() {print("Hello")}
}

func roo() {
  P.foo(A())() // Here
}
@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@AnthonyLatsis AnthonyLatsis added the crash Bug: A crash, i.e., an abnormal termination of software label Dec 12, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. compiler The Swift compiler in itself crash Bug: A crash, i.e., an abnormal termination of software
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AnthonyLatsis