For removal: we have been saying it will happen for a while now, we should make good on it.

k patterns, that is, numeric literals

For removal: Overloaded numeric patterns mean there is hidden computation going on during LHS matching.
Nine times out of ten, what is really wanted is Natural numbers, not Integers (and definitely
never Floats!). This language feature also makes the implementation of code-transformation tools more tricky
and less regular.

Against removal: Everyone uses them. Lots of legacy code. Expressing recursion over numbers is more verbose
without these patterns.

(JL) This would so fundamentally change the nature of Haskell as to make it a different language. It is surely out of scope for what we plan to accomplish.

Helium has no classes, yet is recognisably very Haskell-like.

A concrete proposal would be to replace classes with named dictionaries that can be constructed and passed
around explicitly. See ​NamedInstances. However this would rule out GADT based class implementations such as jhc's.