-
Notifications
You must be signed in to change notification settings - Fork 88
impl core::ops
for core::simd
#5
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
Comments
It needs a rebase, but I have started on this in the |
Also, I think we may want to consider implementing Index/IndexMut as well, which can just delegate to a slice. |
I feel like Index/IndexMut are enough of an accidental performance footgun that you should be forced to call But i've said that before and people keep not thinking it's a big enough deal. So... I mean I guess. |
Ignoring SIMD specifics, from the Rust point of view, I think things that implement Edit: I think we're going to need to adopt a general policy of how easy it should be to write slow code. I think for the sake of portability and convenience we're going to need to allow it, which might include things like |
Yeah, the I guess we'll just allow slow ops and then... tell people somewhere, uh, "i know we let you do it but it's for emergencies only". |
Uh oh!
There was an error while loading. Please reload this page.
Most of these are self-explanitory.
vector op scalar
should "auto-splat" the scalar value and then perform the op between the two vectors. This is just good quality of life / ergonomics.f32
/f64
don't support bit ops. I consider the lack of bit ops on the floating primitives to be a "not cool" part ofcore
.The text was updated successfully, but these errors were encountered: