Uh oh!
There was an error while loading. Please reload this page.
Fix Vector<T> != operator - #78177
Conversation
ghost
commented
Nov 10, 2022
Tagging subscribers to this area: @dotnet/area-system-numerics |
This is closely related to the fix we merged here: #77815. Are there any other locations that might need this fix? Edit: I think not. Vector128, 256, and 512 all use Vector64's implementation. This PR should be the last change needed to fully fix this bug. |
hughbe
commented
Nov 10, 2022
surprised there isn't a test for this? |
filipnavara
commented
Nov 10, 2022
|
hughbe
commented
Nov 10, 2022
Ah... well I think we should also have some deterministic tests IMO |
tannergooding
commented
Nov 10, 2022
We were supposed to have some hard coded tests to cover edges like this, but it looks like they never got checked in. I'll log an issue and track getting this all audited/fixed. |
BruceForstall
commented
Nov 16, 2022
Does this need to get back-ported to 7? |
tannergooding
commented
Nov 16, 2022
No, this was a .NET 8 exclusive change. |
Also fixes#78163