ripytide
ripytide
While I understand that `const fn` is now stable, `const fn in trait` is not yet stable so the example provided of `fn mul(self, r: T) -> Self::Output` is (at...
This issue looks to have been resolved in `v0.8.9`, I'd recommend closing it.
One option would be: ```rust pub trait AnyRgbaPixel { fn r(&self) -> T; fn g(&self) -> T; fn b(&self) -> T; fn a(&self) -> Option; } ``` Then since `a()`...
I think same-language conventions have greater value for code readability than across-language conventions. As such I am in favor of this change.
Also worth adding the `RGB8` -> `RgbU8` suggestion from #62 here for visibility.
> RGB is a super-common acronym `HTML`, `CSS`, `HTTP` are all commonly-known acronyms, but crates that implement their types all use the rust naming conventions for types using them such...
I think the question when integrating `Rgbw` into the `0.9` traits will be whether it should act as a `HomogeneousPixel` or a `HeterogeneousPixel` with regards to the `w` component. Since...
I think this issue can be closed as completed in #107?
Complexity is the enemy of a crate aiming to standardize other crates, as such I suggest we provide only the most simple implementation of the blanket `impl From for Rgb...
> For 0x12 to 0x1212 I propose to use the term extend, a bit like sign-extend. This seems contrary to this crates purpose in being agnostic on semantics, by providing...