|Version 13 (modified by maeder, 6 years ago) (diff)|
|Dependencies||reject NegativeSyntax NegationBindsTightly|
|GHC||[ none ]|
|Hugs||[ partial ]|
|nhc98||[ partial ]|
|others||[ unknown ]|
Resolve more prefix minus application unambiguously by:
- Considering only operators to the right of prefix negation (as currently done only by Hugs)
- Leave prefix minus bind less tight than multiplication (as is currently done)
- one of the following alternative formulations (the essence of this propoasl)
- Do not consider associativities for prefix minus resolution
- Let prefix minus bind a bit stronger than infix minus
- Compatible with current state (fewer programs are rejected)
- fewer cryptic rejection messages involving prefix minus
- All prefix minus applications will be resolved
- Does not explain why and how certain terms are resolved (if they are accepted)
As described in NegationBindsTightly ghc rejects some terms that are accepted by Hugs and Helium and should not be rejected in general. However, making negation bind more tightly is not the proposed solution here, because it would (in my eyes) wrongly resolve "- x ^ 2" to "(-1) ^ 2".
- Only operators to the right of prefix negation need to be considered for resolution.
This condition ensures that "4 * -5" is not rejected (as ghc does).
- Prefix minus should bind less tight than multiplication but …
- .. (slightly) stronger than addition and subtraction.
The latter condition ensures that "- x # …" is resolved as "(- x) # …" for any operator # with lower precedence than multiplication.
"-4 * 5" will be resolved to "-(4 * 5)" as Hugs correctly does already. I don't know how Helium resolves this, but it does (usually) not matter for multiplication if it were resolved to "(-4) * 5".
However, Hugs rejects "-4 # 5" for a non-left-associative operator # with precedence 6, because it compares associativities for operators with the same precedence. Therefore prefix minus should have a (slightly) higher precedence than infix operators with the precedence of infix minus.
infix # 6 (#) = (-) x7 = - 4 # 5
x7 are currently rejected by Hugs and ghc. Two solutions are possible. By accident nhc98 resolves this as "-(4 # 5), because # is not left-associative. I think associativity should only matter for two infix operators. Since "-" should just bind weaker than multiplication "(-4) # 5" should be the unique solution!
infixr # 6 (#) = (-) x8 = - 4 # 5 # 6
x8 will be resolved as "(- 4) # (5 # 6)" like it would for any right-associative operator # with lower precedence, too. For any non-associative operator # "- 4 # 5 # 6" is rejected like "4 # 5 # 6", "-(4 # 5 # 6)" or "(-4) # 5 # 6" would be.
Surely, one can always disallow "confusing" resolutions, but if we reject "- 4 # 5", we can also reject "- 4 - 5" or "- 4 ^ 5". Associativity seems wrong to consider for the unary minus function. (But it is an option to simple use the way of Hugs or nhc98 for ghc, too.)
As a further option it is possible to support multiple prefix minus application. ("4 * - - 5" can be resolved in the same way as "4 * - 5" is).
For other examples see http://www.haskell.org/pipermail/haskell-prime/2010-July/003229.html (it also shows how easy an implementation is)
Mixfix analysis [Aasa95] usually only considers the top-level operators of argument terms. This backs my point 1. above: Do not look to the left of prefix minus, because there is no argument of prefix minus.
Also Isabelle (http://isabelle.in.tum.de/) allows prefix operators to have lower precedence than infix operators. Other specification languages (like HasCASL) do so, too. For instance the logical prefix negation binds stronger than logical connectives but weaker than infix equality or other comparisons. (This does not apply to the "not" in Haskell, because "not" is a plain function, no operator).
Python's power operator binds more tightly than unary operators on its left, http://docs.python.org/reference/expressions.html, -12 results in -1.
My point 3. is backed by the fact that "in case of doubt" prefix application should bind stronger than infix application.
remove "same precedence" stuff
haskellch3.html#x8-220003 "Negation is the only prefix operator in Haskell; it has the same precedence as the infix - operator defined in the Prelude (see Section 4.4.2, Figure 4.1)."
haskellch3.html#x8-280003.4 "Prefix negation has the same precedence as the infix operator - defined in the Prelude (see Table 4.1)"
Possibly refer to haskellch10.html#x17-17900010.6 "10.6 Fixity Resolution"
replace: "The handling of the prefix negation operator, -, complicates matters only slightly. Recall that prefix negation has the same fixity as infix negation: left-associative with precedence 6. The operator to the left of -, if there is one, must have precedence lower than 6 for the expression to be legal. The negation operator itself may left-associate with operators of the same fixity (e.g. +). So for example -a + b is legal and resolves as (-a) + b, but a + -b is illegal."
with: "The handling of the prefix negation operator, -, complicates matters only slightly. (Recall that) prefix negation has lower precedence than infix multiplication. So -a * b resolves as -(a * b) or more importantly -a ^ b as -(a ^ b). Generally, prefix negation extends as long to the right as there are consecutive infix operators with precedences at least as high as multiplication. The operator to the left of prefix -, if there is one, is irrelevant for resolution. So a + -b or a * -b are legal. Prefix negation binds tighter with infix operators to the right of lower precedence than multiplication. So for example -a + b is legal and resolves as (-a) + b."
(Use the algorithm from http://hackage.haskell.org/trac/ghc/ticket/4180)
haskellch4.html#x10-820004.4.2 "4.4.2 Fixity Declarations" states:
"Any operator lacking a fixity declaration is assumed to be infixl 9"
This (surprisingly) makes "- a `f` b" resolve as "- (a `f` b)" for any f without fixity declaration (independent of this proposal). This contradicts NegationBindsTightly.
But as a compromise it is also an option to simple reject terms where prefix minus would not bind tightly (enough), which makes sense for -a ^ b and would force us to write -(a ^ b) or (-a) ^ b explicitly. (Of course one would not want to reject "-a * b", no matter how it is resolved.)