Conversation
Advise to use 1L. Octal syntax error is demoted to lint warning which can be disabled by power number users, who can freely write decimals literals with leading zero.
| nextChar() | ||
| getFraction() | ||
| } | ||
| // 1l is an acknowledged bad practice |
|
|
||
| def bad = 1l | ||
|
|
||
| def worse = 123l |
There was a problem hiding this comment.
I would think 32l is worstest.
There was a problem hiding this comment.
L01, you're right!
|
I guess you could say something about 1igatures and lDEs and 1inters, but l agree we don't kneed to confuse. (Ok, I've been staring down the 🐰 🕳 too long today.) |
|
but what about Polish (which in the monospace font in my browser, anyway, kind of looks like a meerkat scanning for predators) |
|
For Polish notation, we recommend uppercase in honor of Łukasiewicz. |
|
@som-snytt is something wrong here that I don't get a "warning: there was one deprecation warning" meta-warning in the REPL? it doesn't match the behavior of ordinary method deprecations, as shown in this transcript: this came up over at #7458, where @lrytz's PR had in scala/scala we don't have |
|
@SethTisue the refactored REPL doesn't show parsing deprecations; there is a ticket, but I haven't addressed it. |
|
oh ok, it's scala/bug#11402, thanks |
Advise to use 1L.
Octal syntax error is demoted to lint warning
which can be disabled by power number users,
who can freely write decimals literals with
leading zero.
Squash/rebase of #7388