Daniel Henry-Mantilla

- (FWIW, for the OP case, another option would be to make `.fetch_all()` take a `T where &mut T : Executor`)

Currently `0.9.0` is indeed currently the latest version on crates.io so that's a problem. I was able to reproduce the described issue with the following code: ```rust use ::keystone::{ Arch,...

```rust extern "C" { fn fun (arg: &'_ [mut] c_int); } ``` is basically: ```rust unsafe fn fun (arg: &'_ [mut] c_int) { extern "C" { fn fun (arg: *mut...

`Option` is equivalent to `*const T` / `*mut T` in all things, so that change is perfectly valid and leads to cleaner code, except for the lack of `NonNullMut` meaning...

> from `&` or `&mut` to `NonNull` [`impl From

Whether a pointer can be used to perform a write-dereference has nothing to do with it being `*const` or `*mut`, it has to do with its _provenance_, _i.e._, with how...

I think it's a "_moreover_, functors are not C++ compatible" kind of sentence, as in adding extra info rather than deducing info from the previous sentence. I'd personally thus rephrase...

Yeah, the terms in this area are both quite overloaded for some, and quite diverse for others. A C++ functor seems to be what other languages call a _callable_, _i.e._,...

Regarding the `rustc` compiler flag, using `-F` instead of `-D` uses `forbid()` instead of `deny()` (thus preventing code to overrule the lint). One way to pass flags to `rustc` from...

Forcing the usage of a specific formatter feels contrived, though. Maybe "an autoformatting tool (_e.g._ `rustfmt`) must be used". This way the phrasing remains open to alternative formatters that may...