-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Avoid creating closure for asserts #3267
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
Conversation
test performance please |
performance test scheduled: 19 job(s) in queue, 1 running. |
02141bf
to
d852465
Compare
Did you check the bytecode that this does in fact inline? Just being paranoiac here. Otherwise LGTM |
Yes it does inline, but the generated code is a bit larger. |
While compiling I would drop the first commit. The standard library already has this |
I think we can keep the first commit. There are other asserts, where it would be nice to give them a second parameter without fear that a closure will be created. |
performance test failed: Error line number: 16 [check /data/workspace/bench/logs/pull-3267-10-05-20.54.out for more information] |
1 similar comment
performance test failed: Error line number: 16 [check /data/workspace/bench/logs/pull-3267-10-05-20.54.out for more information] |
Performance test finished successfully: Visit http://dotty-bench.epfl.ch/3267/ to see the changes. Benchmarks is based on merging with master (af528a1) |
e2f4be6
to
d852465
Compare
Removed the second commit |
No description provided.