ripytide

Results 149 comments of ripytide

I don't see an alternative to a hard-migration for the `Gray` pixel type, apart from people just deciding to not migrate, which is their prerogative.

`u8`, `u16`, `f32` and `f64` sound good to me for aliases. The specific naming is indeed a pain. My one strong opinion in on `RGBA` vs `Rgba` since the latter...

That sounds good, strikes a balance between the two approaches.

This seems fixed in 30db416

I think I would prefer a more complex doc.rs home page to nicer imports since I can easily skim over types when reading the docs. This is very marginal though,...

From #121 I think another interesting use-case for having everything exported from the top-level is that you can use a `rgb::*` glob import to get every type/trait in the library...

I agree that the types will be rarely used, but don't agree that putting rarely used types into modules is an improvement, as creating a module adds another item to...

@InnocentZero and I have been working on a fork of this project (https://github.com/ripytide/pacdef) for a few months and experimenting with several ideas for improvements and new features. Now I believe...

@moberer The intention was always to make a pull request upstream to avoid splitting the maintenance effort so on. The changes to the public facing configs as well as the...

@thdxr That's due to `pacdef` using cargo features for the arch and apt backends so they are not enabled by default, another thing I've fixed in the fork.