Jacob Lifshay
Jacob Lifshay
maybe something like [the cfg_expr crate](https://docs.rs/cfg-expr/0.3.0/cfg_expr/) could be used to evaluate `cfg()` conditions? This really should be part of the proc_macro library.
> @programmerjake as I understand, that's one half of the puzzle. (Already very helpful!) The other would be to get the current build config and use it evaluating these expressions....
there's https://github.com/rust-lang/keyword-generics-initiative which iirc is also thinking about being generic over mutability
note that there are proposals (such as the Storages proposal) that change `Vec` to use something other than `A: Allocator`, so maybe there should be a comment to that effect...
> The real questions is whether you want to make scalable vectors target-dependent (SVE, RISC-V). Imho scalable vectors should be target independent, the compiler backend will simply pick a suitable...
> Note that vscale is a LLVM thing and should not be part of the RFC. I think it should not be dismissed just because it's a LLVM thing: every...
> Do you want to expose this in Rust or should it be a an implementation detail of the compiler? imho @rust-lang/project-portable-simd should expose scalable vector types with vscale, an...
One important thing that imho this RFC needs to be usable by portable-simd is for the element type and the multiplier to be able to be generics: ```rust #[repr(simd, scalable(MUL))]...