That's a very good idea but it's not universally applicable, a feature needs to
justify its implementation complexity and the training/documentation aspects (a
bigger language is harder to teach etc). Also, when I say something like "I
want to remove X from Nim" I generally mean to provide a better mechanism that
also happens to do / allow for X. For example, `converter` could be turned into
a more general "overloading resolution hook" that is consulted when type
checking a call expression failed. Note that this is just an example, I doubt
an "overloading resolution hook" is what Nim needs...
