-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Introduce a temporary boolean constant for benchmarking #657
Conversation
Why does @taichi-gardener modify files I didn't change even if what I clicked is exactly this PR? |
Cool! Thanks.
Probably not your fault. I'll take a look at this. If this PR ready for review? Please simply request a review from me when you are ready. Thanks. |
It's ready for review. I googled how to request a review on GitHub, and GitHub Help showed
However, my right sidebar only shows
without a button to click. Why is that? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thanks!
|
No, I don't. However, I can re-request a review from you after you self-requested the review and before approving. |
Oh, I saw this on the website above:
|
I'll assume non-Draft PRs are ready for review next time. Thanks for the info. |
I see a little gear on the right of |
Since you have made significant contributions, your role has been promoted from Ultimately I think you will get |
…ced optimizations (taichi-dev#657) * Introduce a temporary boolean constant for benchmarking * [skip ci] enforce code format Co-authored-by: Taichi Gardener <taichigardener@gmail.com>
Related issue id = #656
I'm now using
test_ad_if_mutable
intest_ad_if.py
for benchmarking. It already reduced the number of statements from 96 to 92 :)[Click here for the format server]