Andy Thomson

Thomas did something like this in a much earlier PR.

I've been reading http://web.mit.edu/rust-lang_v1.25/arch/amd64_ubuntu1404/share/doc/rust/html/cargo/reference/config.html You can set vars like ``` CARGO_FOO_BAR=x ``` To get ``` foo.bar = x ``` It would be interesting to try this.

Rust's implementations have to be precise which may relax in the future to allow some overlap. There is a blanket `Nullable` which is less likely to clash with other implemementations....

Yes. This is true. The current interpretation of `Option` is NA rather than `NULL`. Now we have `Rint` and `Rfloat` we might drop this as it is counter intuitive, we...

Perhaps that now we have the scalar types `Rint` and `Rfloat` that handle NAs, we should reserve `Option` for NULL instead of NA and drop Nullable. Would this make more...

We should revise ToVectorValue

Devices do tend to be mutable in Rust. We should change this. I did consider moving the Device methods to a "guard model" where we lock the device, similar to...

Absolutely, devices should be mutable as file handles are in Rust. Currently, Device is only a reference to a device, so Drop does not make sense. I would like to...

We should look at a guard model to encapsulate mode.on and mode.off.

Thanks, Dario. I would suggest changing const uint32_t pitch = width * bytesPerPixel; const uint32_t faceSize = pitch * height; For const uint32_t pitch = width * bytesPerPixel; const uint32_t...