-
Notifications
You must be signed in to change notification settings - Fork 280
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
fix: don't copy unit registry if it is already the same thing #3180
Conversation
369829b
to
e88aba9
Compare
It turns out this change doesn't do much. It's one of those cases where you cannot trust a profiler (whether it's pyinstrument or line_profiler)
I really wish I could say I shaved 40s off, but:
While I still believe this change is "the right thing to do"^{TM} it's suddenly way less exciting... |
@Xarthisius do you still think this is worth merging ? |
I think this is still worth merging. |
sounds like we're at two implicit approvals. I'll formalise mine |
I'll admit: I don't know what I'm doing. If this gets merged in, there is a chance some unnamed PhD student will probably lose a couple of weeks trying to debug a subtle issue of nonconforming units somewhere affecting their results. They'll
git bisect
and thengit blame
and learn my name. They won't know me, but they'll hate me. With passion.However, on a slim chance that what I'm suggesting doesn't break the Universe horribly, let's run a full testsuite on this PR. Afterwards, I'll provide a concrete example how this benefits a specific use case.