ZayadNimrod
ZayadNimrod
This should address the suggestions re: error messages. That said, this requires compile-time construction of those strings (using `format!` means constructing a string every time an error is raised, and...
Not quite comfortable with erasing error sources like this so I'm keeping the commit in until a last-minute history squash.
Unsure if bc144f0d412db2da66c31f05936216a16504afa7 should make it in, since it should result in extra lookups to the metatable. But it does make the code more compact and less duplicated. Either way...
Sorry to ping again, but it's been a month, any thoughts on this before I add the remainder of the arithmetic methods?
Is this worth adding to the log in `changes/`?
> There's a slight variation that's possible where we just set the mode to whatever the file says, and don't error out, if you were interested. Actually now you say...
OK, I've moved to the mode-changing solution instead, and based on `release` instead, since this shouldn't break anything from the user's perspective.