Skip to content

x ~/ y should allow doubles in compile time constants #1781

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

Closed
floitschG opened this issue Feb 21, 2012 · 6 comments
Closed

x ~/ y should allow doubles in compile time constants #1781

floitschG opened this issue Feb 21, 2012 · 6 comments
Assignees
Labels
legacy-area-analyzer Use area-devexp instead.
Milestone

Comments

@floitschG
Copy link
Contributor

Example of a program dartc rejects, but that should be allowed:
===
final x = 5.5;
final y = 2.2;
final z = x ~/ y;
main() => print(z);
===
file:bug.dart:3: Expected constant expression of type int, got double
     2: final y = 2.2;
     3: final z = x ~/ y;
Compilation failed with 1 problem.

@floitschG
Copy link
Contributor Author

just opened issue #1781.

@floitschG
Copy link
Contributor Author

correction: issue #1782

@kasperl
Copy link

kasperl commented Apr 17, 2012

Removed Area-Compiler label.
Added Area-Analyzer label.

@danrubel
Copy link

danrubel commented Jun 4, 2012

Added this to the M1 milestone.

@bwilkerson
Copy link
Member

Set owner to @bwilkerson.
Added Started label.

@bwilkerson
Copy link
Member

http://codereview.chromium.org/10535148/


Added Fixed label.

@floitschG floitschG added Type-Defect legacy-area-analyzer Use area-devexp instead. labels Jun 13, 2012
@floitschG floitschG added this to the M1 milestone Jun 13, 2012
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
legacy-area-analyzer Use area-devexp instead.
Projects
None yet
Development

No branches or pull requests

4 participants