Changes between Version 12 and Version 13 of PrefixMinusResolution
 Timestamp:
 Jul 15, 2010 7:59:16 AM (5 years ago)
Legend:
 Unmodified
 Added
 Removed
 Modified

PrefixMinusResolution
v12 v13 71 71 72 72 x8 will be resolved as "( 4) # (5 # 6)" like it would for any rightassociative operator # with lower precedence, too. For any 73 ''nonassociative'' operator # " 4 # 5 # 6" is rejected like "4 # 5 # 6" or "(4 # 5 # 6)" would be.73 ''nonassociative'' operator # " 4 # 5 # 6" is rejected like "4 # 5 # 6", "(4 # 5 # 6)" or "(4) # 5 # 6" would be. 74 74 75 75 Surely, one can always disallow "confusing" resolutions, but if we reject " 4 # 5", we can also reject " 4  5" or "` 4 ^ 5`". … … 125 125 126 126 This (surprisingly) makes "{{{ a `f` b}}}" resolve as "{{{ (a `f` b)}}}" for any f without fixity declaration (independent of this proposal). This contradicts NegationBindsTightly. 127 128 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.)