Ideas for reduced compile times about rust-skia HOT 1 CLOSED

These are good ideas and I appreciate that you care. Here are some of my initial arguments, which may be wrong, outdated, biased, and therefore - of course - open for a more detailed discussion:

• Relying on an external curl command would rule out platforms on which curl is not installed (what about Windows?). Also ureq is required when the feature svg is enabled (we may switch to reqwest in the future).
  It's probably possible to create a new skia-bindings feature that replaces the use of ureq with a curl invocation, a PR would be great.
• The bindings file and some of the structures are platform dependent, this is because Skia uses a wide range of C++ includes. Not sure how this can be solved without breaking backward compatibility, specifically if C++ types can be used as transmutable Rust values. A first step would try to export only structs to Rust that are platform independent and adjust the wrappers for the rest.
• Using skia-sharp's C bindings would mean to rewrite all the Rust wrappers. And as you've noted, SkiaSharp was never good in keeping up to date with Skia in the past, which means to me that the only option is to take over maintenance of the C bindings, which may be a worthy attempt for another Skia binding project, but out of scope for rust-skia for the time being or as long I can't see a clear migration path.

from rust-skia.