Caleb Zulawski
Caleb Zulawski
I guess I should note that the `suggested_simd_width` function isn't perfect, it certainly can't recognize unusual things like some AVX implementations being slower than others, however in the context of...
On master, the clones are now completely contained within the multiversioned function, which solves this issue. It also helps some more peculiar cases, like multiversioned trait implementations.
Sorry it's been a while--this has been added to master. The new API actually allows selecting any target CPU, such as `"x86_64/skylake"`. Currently, x86-64-v3 doesn't work because `std::arch` lacks detection...
Another new feature has been added that allows you to specify `#[multiversion(targets = "simd)]`, which automatically selects from all SIMD instruction sets. On x86/x86-64 this corresponds to the microarchitecture levels.
This library has been effectively deprecated in favor of `std::simd` in the nightly compiler. I would accept a pull request but unfortunately I don't think there is anyone with time...
> I'm working on a feature system for Bazel modules (similar to that from Cargo), which could be a way to make this configurable. That sounds great, exactly what I...
I unfortunately had to remove support for functions that took `self` or referenced `Self`: https://github.com/calebzulawski/multiversion/releases/tag/0.7.0 The previous implementation was buggy and conflicted with other changes necessary for the 0.7 release....
Could this setting at least be overridden with an environment variable? I have a `rules_$company` module that is used by maybe a dozen separate repos that establishes uniform toolchains and...
Perhaps what I need for my use-case is to transform env.yaml to include channels and default packages, which should have a similar result. I could also see this as similar...
It should be possible--in my use case it happens that the condarc is controlled by a build system and the dependencies are defined by the user, so that's why I...