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

Measure impact of global type inferencing on largish standalone benchmark #5978

Closed
kasperl opened this issue Oct 17, 2012 · 7 comments
Closed
Assignees

Comments

@kasperl
Copy link

kasperl commented Oct 17, 2012

Let's get some numbers on the compile-time performance impact of enabling global type inferencing. Of course, knowing where it helps on generating smaller and faster code would also be good.

@polux
Copy link
Contributor

polux commented Oct 17, 2012

Added Accepted label.

@peter-ahe-google
Copy link
Contributor

Removed this from the M2 milestone.
Added this to the Later milestone.

@kasperl
Copy link
Author

kasperl commented May 23, 2013

Added TriageForM5 label.

@kasperl
Copy link
Author

kasperl commented May 28, 2013

Removed TriageForM5 label.

@kasperl
Copy link
Author

kasperl commented Jul 10, 2014

Removed this from the Later milestone.
Added Oldschool-Milestone-Later label.

@kasperl
Copy link
Author

kasperl commented Aug 4, 2014

Removed Oldschool-Milestone-Later label.

@karlklose
Copy link
Contributor

Global type inference is the default in dart2js.

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

No branches or pull requests

4 participants