Caleb Zulawski

It's been a while, but related to #33, I'm working on a branch in which the following is now possible: ```rust #[multiversion(targets = "simd", selected_target = "TARGET")] fn foo(x: &mut...

The intention of this, of course, is to work with portable SIMD, so you can do something like ```rust const WIDTH: usize = TARGET.suggested_simd_width::(); type Vector = std::simd::Simd; ```

I do plan on making new releases, so I'll make sure to update the docs when I do.

I just ran into the same issue (`-Wl,rpath,$$ORIGIN/../lib`) with cmake and came to file an issue.

I just ran into this, it would be nice to have fixed! As a workaround, this very simple patch seems to work if you're only interested in building flatc/cc library:...

It appears that adding `CONDA_SUBDIR` convinces micromamba to use the right subdir, so I don't think it should be too hard to apply the same logic based on whatever `platform`...

I'll have to try Conda on Monday. It looks like the equivalent Conda setting is `subdir`, not `platform`, but I'll need to try it out. For what it's worth, the...

This has been implemented on master (in fact, you can specify any target CPU now). Unfortunately, Rust doesn't properly support MOVBE yet, so x86-64-v3 doesn't work. See the comments in...

On master, there are new `target_cfg` and `target_cfg_attr` macros that should work as expected. They are regular macro attributes, so should not have scoping issues within other macros. Additionally, `target_cfg`...

This has been added to master as via the [`target-features` crate's `suggested_simd_width` function](https://docs.rs/target-features/0.1.1/target_features/struct.Target.html#method.suggested_simd_width). I'm _pretty_ sure this is usable with `std::simd` without any additional nightly features (as long as you...