Philipp Korber

You might also want to consider adding some support for RFC2231. Currently you can parse/uses MIME conforming with the RFC, but you have to put extra work on top for...

Here are some other thinks which I think are a good idea: 1. do not use `Name` for both names and values. All "names" are can be compared case insensitive...

Mime in _Mail_ can actually have tabs in practice[1] (and `"\r\n "` / `"\r\n\t"` sequences if the content type is split over multiple lines...). For mail " " is basically...

In the fork [here (github)](https://github.com/1aim/mime/tree/parser_revamp/src) (note it's in a branch) I have rewritten the parser, and ended up rewriting large parts of the mime crate. (note documentation is not yet...

update: It should be easy to implement I just have to change the Spec trait slightly, turning `parser::parse` into `::parse` and moving some parts of the Spec trait to a...

There are two features in python3(only) witch change the signature of a function. PEP3107 allows you add annotations to parameters and return types when defining a function (with `....parametername: annotation...`...

One argument against `application/x-msgpack` is that there is probably also `application/x.msgpack` out in the wild (I mean that is given RFC6838 the right think to use until msgpack is registered)...

Same for "releses". Through that isn't even an English work as far as I can tell?! (It's a Galician word so it might appear in some of the default dictionaries,...

I think `Context` shouldn't really be called `Context` but `Chain` (and as such the names of `context` and `with_context` would also change). I recently changed a not so small crate...

Expect what I already mentioned about `context` another think I think could be improved if the name is changed anyway is to not use a `with_` prefix. All places in...