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

Common task: run tests #19

Closed

sethladd opened this issue Sep 14, 2014 · 1 comment

Collaborator

sethladd commented Sep 14, 2014

No description provided.

devoncarew mentioned this issue

working on running tests #42

Merged

Contributor

seaneagan commented Apr 17, 2015

Merging into #58.

seaneagan closed this as completed

jcollins-g pushed a commit to jcollins-g/grinder.dart that referenced this issue


          Rework how expressions are scored.

This moves away from tuned split costs to unit-cost spans.
Those compose better, which yields better results in nested expressions.
Some of the existing tests get changed because the old output is better now.

Fixes google#6. Fixes google#19. Fixes google#25. Fixes google#28. Fixes google#55. Fixes google#81. Fixes google#91. Fixes google#95. Fixes google#98. (!)

R=pquitslund@google.com, sigmund@google.com

Review URL: https://chromiumcodereview.appspot.com//824693005

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