Difficult to introduce fallbacks when parseQuality fails

[zmthy]

Difficult to introduce fallbacks when parseQuality fails

[zmthy]

Okay. I think I might actually just make the argument a string and reuse readQ. I won't have time to get on top of this for at least two weeks but it should be a pretty simple addition.

[zmthy]

Are you ever building quality values that don't have a quality of 1?

[Zankoku-Okuno]

Re building non-1 quality values: I think it's possible. My current use-case can afford to be a toy, but I could easily see someone building a server that fills in a default accept header along the lines of text/html,*/*;q=0.9.

[zmthy]

Okay, I've pushed to develop. I've exposed the maxQuality and minQuality functions, as well as a new quality function that uses readQ with a default error message. I've also prepped to bump the version to 1.0, let me know what you think and I'll finalise the release and publish to Hackage.

[zmthy]

Totally forgot about this. Let me know if you have any thoughts, I'll push the release soon.

[Zankoku-Okuno]

Well, you're not alone in forgetting :)

I think this kills the issue. I was going back-and-forth on whether an IsString instance would be good, but IsString a => IsString (Quality a) seems way too general to be a good idea.

I did have an unrelated idea before you publish, which I've put in #21 for organization purposes.