Skip to content

Option parsing is broken #323

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.

Sign up for GitHub

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
Closed
smarter opened this issue Jan 6, 2015 · 4 comments
Closed

Option parsing is broken #323

smarter opened this issue Jan 6, 2015 · 4 comments

Comments

@smarter
Copy link
Member

smarter commented Jan 6, 2015

dotc -target:jvm-1.7 doesn't work, it seems that one needs to type dotc -target jvm-1.7 which is different from scalac
@DarkDimius
Copy link
Contributor

fyi: java1.7 target is NOT supported by dotty. Backend assumes at least java 1.8(encoding of traits assumes presence of jvm 1.8 default methods, closures are always compiled to jvm 1.7 lambdas).

@smarter
Copy link
Member Author

smarter commented Jan 6, 2015

Right, it's just the first example I found :)

@felixmulder
Copy link
Contributor

@smarter: is this still broken?

$ ./bin/dotc -target:jvm-1.7 file.scala

Works fine (even if it doesn't do anything with the java 7 choice).

@smarter
Copy link
Member Author

smarter commented Jun 2, 2016

Fixed by #1180

@smarter smarter closed this as completed Jun 2, 2016
tgodzik added a commit to tgodzik/scala3 that referenced this issue Apr 29, 2025
@tgodzik
Merge pull request scala#323 from scala/backport-lts-3.3-22793
8f555e5 
Backport "Reword reference article about type projection so that it highlights what is allowed" to 3.3 LTS
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@smarter @DarkDimius @felixmulder