Matej Knopp

Few things here: 1. I'm wondering if the inconsistent delivery had a root cause that we missed while adding a really complicated workaround - for example running CADisplayLink on main...

A lot of stuff changed since the touch resampling workaround was implemented (including not using CAMetaLayer anymore and always running display link on main thread), plus several iOS updates, so...

I don't mind optimizing by default, but maybe we should have at least an option to do -Os. In my experience the performance difference is in most cases negligible and...

> Great idea. Yeah so an enum with descriptive messages makes sense. (We don't really have to share them across the different native_toolchain packages, but it would be good if...

Technically we can override cargo profile optimisation levels specified in `Cargo.toml` through environment variables (i.e. `CARGO_PROFILE_DEV_OPT_LEVEL`), but for me as a package author that'd be quite unexpected if the builder...

This looks good to me, even though I'd probably prefer `-Os` to `-O3` as default. Though not a hill I'd die on. I think it's a better balance to have...

This would certainly need some changes in `native_toolchain_rust`. I'll do my best to accommodate those. Missing pieces seem to be custom cargo arguments and static library. I'm not sure what...

@mosuem, I published 0.1.0-dev.7 which supports extra cargo arguments. No support for static libraries, but I think I'd wait with that until there is actual support in native assets. Is...

> Thanks - let me take a look. > > > No support for static libraries, but I think I'd wait with that until there is actual support in native...

I see. That should be fairly easy to add. The remaining thing is the assumption that builder is always building a dylib.