Jake Goulding
Jake Goulding
Alright, three potential solutions for you: https://github.com/shepmaster/json/tree/never-return-negative-depth https://github.com/shepmaster/json/tree/call-to-json-like-pure https://github.com/shepmaster/json/tree/local-depth-variables-like-c-ext
> It turns out that not all x86 cpus have the cpuid instruction While technically true... > [CPUID] was introduced by Intel in 1993 when it introduced the Pentium and...
Yeah, this is probably a good idea. I might rather roll our own detection, as cpuid appears to be a binding to another library, which seems like a large requirement...
Basic beginning in [cpuid-rs](https://github.com/shepmaster/cpuid-rs).
An interesting question - at what level should this check be done? There are two I can think of: 1. At compile time, via a custom build script. 2. At...
Of course, there's always "add more feature flags" to support both options...
All of this absolutely makes sense. I actually thought there was an issue for this already, as I'm sure someone else wanted it. > run a search on a `&[u8]`...
@BurntSushi what kind of API would you like to see? Strings are nice in that they have the `Matcher` API to bolt into. Byte slices don't seem to have the...
> I think a macro would be regrettable. The macro is to allow for fallback cases where the intrinsic operations aren't available. _Technically_, I could make a few small changes...
> Thanks for working with me on this btw. Absolutely! Having people use the library is the only way it will get better! And the faster Rust is, the more...