I don't know the answer, but it behaves according to what I would expect here. I normally think of unary minus as having the same precedence as plus and minus. Compare to −1² being −(1²) in mathematics, and a + b.to_int() being a + (b.to_int()), not (a+b).to_int().
Similarly, if I type -a.to_int(), I definitely want -(a.to_int()) and not (-a).to_int(), and it would be really inconsistent if -9i32.is_positive() behaved differently from -a.to_int().
On that I have to disagree: -1 to me is a single, defined integer value (Rust parsing notwithstanding) that can directly be translated to an all-1s bit pattern (on 2s-complement machines) at compile-time, whereas -a is an expression that needs to be evaluated at run-time.
Edit: Come to think of it, the current approach is inconsistent in its own way: -128i8 shouldn't be a thing - it would be the negation of 128i8, but that is outside the value space of an 8-bit signed integer.
I think you're somewhat missing the point, which is that -𝛼.method() is always parsed as -(𝛼.method()) and never (-𝛼).method() regardless of whether 𝛼 is a literal, a variable, or some more complicated expression. That seems nicer to me than having a different rule for the - in negative literals. (It's also how it works in Python, which is the language I use most often.)
That is a bit weird, yes, but it still works mathematically, so it doesn't bother me that much personally. (I.e., 127i8.wrapping_add(1).wrapping_neg() == -128i8)
I get that that's the way it is. The disagreement is that I, personally, think that a negative value should be a single literal and token. The way it is, it's literally (heh) impossible to write literals for half the value space of signed integers.
IMHO that's more than a bit weird: I'm not writing 127i8.wrapping_add(1), I'm writing 128i8, and if I leave it at that I get a compiler error. I still get an error if I write std::ops::Neg::neg(128i8). Yet I am able to write -128i8 and suddenly it works, even though by rights it should be treated the same.
I can see this from both the mathematical and parsing points of view.
Ultimately it looks like there's a tension between the 2, and resolution seems to require picking one or the other.
Having said all that, going with the mathematical view would require context-sensitive parsing in order to make an exception for numeric literals. Context-sensitive parsing is a big no-no for modern programming languages (and yes, that means that I exclude C++ from that group of modern languages) for reasons of implementation complexity, theoretical limits of what you can do with the grammar of such a language (more expressive generally means more expensive to compute and manipulate) and probably reasons of simplicity in terms of usage, since it is much easier to remember a rule that applies everywhere than it is to remember "in situation A this goes, but in situation B that other thing goes, because of reasons".
I don't think that treating -9 as an operator and a literal 9 is in any way in conflict with a "mathematical" perspective. In mathematics there's no difference between the number -9 and the unary minus operator applied to the number 9; they're the same thing.
If you see -9! or -9² in a mathematical context you should certainly not interpret them as (-9)! and (-9)².
That said, this is really nothing more than a convention. Rust had to choose something and it went with the Python (more mathematical?) interpretation instead of the Ruby (more pragmatic?) one. There's nothing to gain here from arguing about how it should have been different.
(I suppose there could be a rule that negative literals always have to be parenthesized.)
But I also think that the point that there's no literal for half of the value space of any i-literal (e.g. i8, isize etc) is a valid one, and it creates a couple of weird corner cases such as the one lined out above.
Note, however, that 0 - 128i8 doesn't compile out of the box, either.
Also, 3.9e-8 is parsed as single token/literal, even though it stands for 3.9 * 10-8, a much more complex expression, including a negative value in the exponent. No unary operator required there. So the mathematical argument doesn't seem entirely water-tight, either.
Edit: INB4: I do acknowledge the arguments for the unary operator, besides it making parsing things like
- /* auto-generated comment */ 28i8
much less hairy.
... Then again, 3.9e+compute_exponent() would be fun to see...
Yikes. I think you may have just made his point for him (at least to me).
So, -128i8, will not parse, or, if you disable the lint you recommended it will have the value -((-128)i8) which is 128i8 which is (-128)i8 (via overflow). This seems like a crazy thing to have the compiler go though.