Lukas Wirth

This is just an info issue giving quick access to the changes between the current blend2d master branch and the commit the current submodule in this repo points to: https://github.com/blend2d/blend2d/compare/9572324a3899099add0dceeac2f0b263d04374ca...master

It generates bindings on my machine just fine but for some reason it isnt working anymore on travis, ex.: https://travis-ci.com/Veykril/blend2d-rs/jobs/270665635

The current error implementation just wraps the C error codes and thats it. The display implementation currently just returns the variant names, it would be nicer to have proper descriptions...

It would be really interesting to have a way to implement own encoders and decoders implemented in rust to be used by blend2d. One thing i think would be quite...

Some objects can be constructed with external data, those functions take a function pointer to clean up the data when it isnt needed anymore. I am not sure how one...

Related source can be found here: https://github.com/blend2d/blend2d/blob/69141350b5a654f328c8529ae301aa1e6bad5342/src/blend2d/blpixelconverter.h

Regarding color things, we currently just use u32s and u64s which isnt that nice to use in most cases. It would be nice if we had something to the C...

The way gradient's constructors work rn forces one to specify the generic GradientType since the compiler cant infer which type comes from the given ValuesType since a GradientType defines what...

Currently most things that can make use of I/O do so through the C side of blend2d. It would be nice if these things could also maybe offer an api...

While the project already has all the [getting started examples](https://blend2d.com/doc/getting-started.html) ported it would be great to have even more, even better if we had a similar program for testing like...