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

Compiler Crash with > as a property #4766

Closed
scabug opened this issue Jul 4, 2011 · 6 comments
Closed

Compiler Crash with > as a property #4766

scabug opened this issue Jul 4, 2011 · 6 comments
Assignees

Comments

@scabug
Copy link

scabug commented Jul 4, 2011

Using > as a property that returns a number causes the compiler to crash.

object Bug extends App {
  val x = new {
    def > = 1
  }

  println(x>)
}
@scabug
Copy link
Author

scabug commented Jul 4, 2011

Imported From: https://issues.scala-lang.org/browse/SI-4766?orig=1
Reporter: Jan Kassens (kassens)
Attachments:

@scabug
Copy link
Author

scabug commented Jul 4, 2011

@retronym said:
please reopen in the 'Scala' project. INF is for meta issues with Jira, etc.

@scabug
Copy link
Author

scabug commented Jul 5, 2011

@soc said:
@jason: The bug is listed as #4766. Is there anything I'm missing here?

@scabug
Copy link
Author

scabug commented Jul 5, 2011

Jan Kassens (kassens) said:
@simon: I moved the bug from INF to SI.

@scabug
Copy link
Author

scabug commented Jul 5, 2011

@soc said:
Right, I see. Sorry, just saw "resolution: invalid".

@scabug
Copy link
Author

scabug commented Nov 8, 2011

Commit Message Bot (anonymous) said:
(extempore in r25965) Fixing logic in structural types.

Check number of arguments before jumping to conclusion that
a primitive seeming structural call might really be primitive.
Closes #4766, no review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants