-
Notifications
You must be signed in to change notification settings - Fork 1.1k
-Xlint 1l #14753
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
-Xlint 1l #14753
Conversation
probably it was based on upstream/master, the first commit is last June. Or not. Also the check file update failed. Ah, the line lengths are different.
|
15c6e6e
to
21e0132
Compare
Converting to draft until I understand github actions and how to reproduce the scaladoc build failure. |
21e0132
to
d8f9bd0
Compare
The tweak to make
presumably to do with how scaladoc extends settings, but I did not track it down. The urgency is to introduce a linting option. Any linting option. Aliasing Or, as an alias, we should say "you phoney". |
community build reminds us that perhaps they'd like to turn off a lint:
edit: context:
|
An additional message is emitted on `0_x` because it asks to continue, but that is helpful.
Align with Scala 2 and improve subsequent parsing.
d8f9bd0
to
533d613
Compare
Add
-Xlint
setting andEnumSetting
andonUpdate
to enable post-processing such as linking another flag.-Xlint
can enable-deprecation
, and-Xlint:longlit
deprecates1l
. (It is regular deprecation on Scala 2, but treading gently.)Eventually
EnumSetting
will want to avoid string comparisons.The
FromDigits
error handling is a regular error because otherwise subsequent parse is worse.Forward porting from
scala/scala#4182
scala/scala#7685