-
Notifications
You must be signed in to change notification settings - Fork 199
Fix #351 #353
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 #351 #353
Conversation
Thanks for the quick turnaround. I am having problems with this patch. Looks like they can be reproduced with |
I knew this wasn't that easy to fix, otherwise I would have already fixed it... |
I see what is happening, your |
If that all seems like too much to bury beneath a simple |
Yes, because it’s indeed really not clear what |
To me, it feels like |
Not my finest work, but it should work now. |
Thanks, almost there. One last consideration for the complex case. The discrepancy there is smaller, but not irrelevant.
|
Of course... my bad, should be alright now. |
Looks good! So this operator will remain a part of FF and I can safely use it in my code (without fear of deprecation)? |
It can stay, but it comes at a cost of three vectors instead of a single one (for now). So the user-facing code is maybe clearer, but slightly more memory-demanding under the hood (of course, these are merely vectors, so it should be in no way a bottleneck for most codes). |
Got it. Thanks for your quick work. 5-star service 😊 |
No description provided.