Hi
Re ! as an operator: This caused a number of complexities in the
parsing of stuff, including shift-reduce conflicts. Someone would need
to look into this, and determine that the rules are completely
unambiguous.
Backwards compatibility requires that it be implicitly imported from
Prelude
The bang pattern proposal [1] still allows (!) to be used as an
operator. I think there should be no difference in this regard between !
and ~, since they are used in exactly the same location.
In my opinion the best thing would be to allow (~) and (@) as operators.
With the same restriction
Twan van Laarhoven wrote:
The bang pattern proposal [1] still allows (!) to be used as an
operator. I think there should be no difference in this regard between !
and ~, since they are used in exactly the same location.
In my opinion the best thing would be to allow (~) and (@) as operators.
Isaac Dupree wrote:
Twan van Laarhoven wrote:
Oh, and while we are at it, I think (:) should also be removed as a
reservedop, there is no reason for it to be on that list.
Backwards compatibility requires that it be implicitly imported from
Prelude even in a module that does import Prelude (
