nwin
nwin
That’ll be nice but we would need to be very picky about the test images. We don’t support these fax encodings, no jpegs, etc. That I didn’t add a test...
I don’t think so. You have the same ambiguity problem when matching against lower-case enum variants and there is no warning emitted for that.
I think there are two things to agree on: 1. What is the purpose of `non_upper_case_globals`? Warning about naming conventions or ambiguity? 2. Do we want to warn about ambiguity...
What else would you propose to use if no color space information is given? Just averaging all values?
@kryptan I added this to [`image_buffer`](https://github.com/PistonDevelopers/image_buffer/blob/master/src/color_model/gray.rs#L22). Here, `Rgb` is defined to be in linear color space (scaled to 1.0) and `Rgb` in gamma compressed color space. Converting between this two...
@bvssvni can you make me the owner of `inflate` as well? Just tried to publish myself, didn’t work 😄
Ok, I published an update to the crate.
Not broken, just not supported by rustdoc (yet? ever?).
I filed an issue https://github.com/crabtw/rust-bindgen/issues/212
I think it should be solved like in koma-Script (latex). There you can define a variable named `backaddressseparator`. The address is there separated by line breaks, which would also seem...