Ralf Biedert

Yes, you are probably correct. Most it not all `faster` functions are `#[inline]`. Maybe it could just report that it didn't find anything, plus what you said, e.g.: ``` No...

Thanks for the hint! For testing purposes I also added a non-inlined method `test` to the faster crate, and now things show up: ``` ::get_type_id ::box_me_up ::get core::ptr::drop_in_place faster::test ```...

Just an update that I'm a bit stuck. The good news is, with the latest changes in [packed_simd](https://github.com/rust-lang-nursery/packed_simd) I was now able compile a `faster` core, that doesn't rely on...

Unless I'm mistaken this doesn't look like an easy fix: `std::simd` types such as `float32x4` seem to `impl` functions like `abs()` directly. That means we can't easily re-implement them in...

After changing a few lines in `vektor-gen`[1] it seems to have generated wrappers for `aarch64` and friends [2]. I am now looking at `faster` again, and there are quite a...

Great! How do you want to handle this? I don't mind trying something that gets thrown away if it doesn't fly. However, if you are working on this already (and...

I made some changes now, up for discussion: https://github.com/ralfbiedert/faster/tree/more_archs - There are 2 top-level folders now: `arch` and `intrin`. - `arch` contains implementation details for each architecture. Currently it holds...

Alright, I now have a version that compiles and "mostly works" for `x86` and `unknown` architectures. The latter should compile for any architecture (sans endian, haven't thought too much about...

Thanks for the feedback. My reasoning so far has been documenting "common operators one would know coming from another language" does not really explain anything to our target audience (experienced...

> What about using the [Table B-1](https://doc.rust-lang.org/book/appendix-02-operators.html) from the rust book? I don't think that table fits as-is, I'd still start experimenting with some format mentioned above.