This morning I was scratching my head over failing Rust code that turned out to be due to Rust parsing "-1" as the literal "-1" (good!) but "-1.x(0)" is parsed as "-(1.x(0))" (bonkers!). Turns out that it's a known issue, but blimey is parsing hard! https://github.com/rust-lang/rust/issues/117155
=> More informations about this toot | More toots from ltratt@mastodon.social
@ltratt I am increasingly of the opinion that a unary negation operator is a bad idea. The number of times I've written something like x = -x is so small that changing it to x = 0 - x is no hardship (and, the last time I wrote it, I actually did write it like that because it was clearer). Removing the unary negation operator would make that an unambiguous parse because -1 is a valid number literal, whereas - {expression} is not a valid expression. Similarly, x-1 is unambiguous (x {-1} is not valid).
=> More informations about this toot | More toots from david_chisnall@infosec.exchange
@david_chisnall @ltratt note that for fp numbers -x
is not strictly equivalent to 0 - x
, which is perhaps a small spanner in the works there (though certainly not a big one, you can always implement it as a negate function without the operator).
=> More informations about this toot | More toots from dotstdy@mastodon.social
@dotstdy @ltratt If you're writing floating-point code that relies on that difference, and I ever have to read it, an explicit call to a function called fneg or something more descriptive would make me very happy.
=> More informations about this toot | More toots from david_chisnall@infosec.exchange
@david_chisnall @ltratt yeah, 100%. Having a special function gives you a place to put documentation of the semantics too.
=> More informations about this toot | More toots from dotstdy@mastodon.social This content has been proxied by September (3851b).Proxy Information
text/gemini