| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
fix encoding to show euro-sign correctly.
(cherry picked from commit 13054daa658484df30b71447dbe684f475537252)
|
|
|
|
| |
(cherry picked from commit 68b16a0992877b4ebbb7c967804edbb72c05ceb5)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit changes all first sentences of library functions which
contain `i.e.` or `e.g.` and adds a `,` to prevent that the scaladoc
summary sentence is cut after this abbreviation.
This is possible as pull/3824 fixed how Scaladoc parses the first
sentence of a method description into a sumary sentence(now the first
sentence has to end with a dot followed by whitespace).
Only docs in the core library are changed (src/library/**/*.scala)
and only if they occur in the first sentence.
Review by @heathermiller
(cherry picked from commit 72721ff5dd06dea1235ecb71acae0bd61aee4814)
|
|
|
|
| |
(cherry picked from commit 7cca7635b392cb533d0f8e26b74d7362c0dd3891)
|
|
|
|
|
|
|
|
|
| |
scala.math.PartialOrdering.
- Previous (misleading) documentation suggested that a partial ordering *is* an equivalence relation. This has now been clarified.
- Existing documentation on properties of partial orderings (reflexive, transitive, antisymmetric) had several formatting inconsistencies that have now been remove.
(cherry picked from commit 528df5becee03175e7462b64d7c22460cc5992f7)
|
|
|
|
| |
(cherry picked from commit 0a1694d8048f01b7f0812cedaa341813e9044e7f)
|
|
|
|
|
|
| |
given by som-snytt.
(cherry picked from commit ec4abf5483e890976ae460252e80a66a95674e61)
|
|
|
|
|
|
| |
Scaladoc places the first sentence in the method summary table and index. The first sentence is defined as the sequence of chars up to the first period (not as in JavaDoc where the sentence ends with the first period *followed by a blank*). As a consequence, the clause starting with `i.e.` is interpreted as sentende delimiter. This request replaces `i.e.` with `i.e.`. Alghough a valid HTML code, I do not know whether this change is compatible with other tools. And I assume that this is not the only source file affected.
(cherry picked from commit c2e4da674d8c40e2d220854a966b0510fb6d459e)
|
|
|
|
|
|
| |
Option.collect methods.
(cherry picked from commit e3311073bbad6f6f0dfdd3ea09628d324b4b3614)
|
|
|
|
| |
(cherry picked from commit 1e2a21681a4a55469faa59b07473a3b269e70258)
|
|
|
|
| |
(cherry picked from commit 6c698089aeb55e649a65dd7ae1bce2b4514ee865)
|
|
|
|
|
|
|
|
|
| |
See e2a3498 commit message for explanation
Explicit private declaration better than implicit
Thanks to @som-snytt
(cherry picked from commit d071abe8dd9035d8dd246ecb6b207e584b6437fa)
|
|
|
|
| |
(cherry picked from commit 80a9e908fd7b591a6fe452d908407d537675a999)
|
|
|
|
| |
(cherry picked from commit 71bc2e5f4c49463a754a6f23e3abd2d27467fca4)
|
|
|
|
|
|
| |
caller is responsible for checking 'isDefinedAt'
(cherry picked from commit 455bcd65c055119f928b3367839f0093cf0e251a)
|
|
|
|
|
|
| |
caller is responsible for checking 'isDefinedAt'
(cherry picked from commit f7d2cec3a0c31836747a25e3cc5949d1f3cbdff4)
|
|
|
|
| |
(cherry picked from commit fd001811c662f6daecf91319b36c1ad14a87ff72)
|
|
|
|
|
|
| |
Corrected api doc for >> operator to say it bit-shifts right rather than left, and fills the left bits rather than the right bit
(cherry picked from commit 17b99e2587251cdb02e9d96fc2f87143be3160b8)
|
|\
| |
| | |
remove jline sources from src/ now that we use a released jline.
|
| |
| |
| |
| |
| |
| | |
We don't need those, right?
We don't even build that folder anymore (since 1b0fa91), it is just dead
code.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This mode of macro expansion is used by the presentation compiler to
leave the original macro applications ("expandees") in the type
checked trees, annotated with the types of the expansions.
However, under some circumstances involving implicits, we would
re-expand the macro. If the macro wasn't stable, this could lead
to a type mismatch.
The originally reported problem was with the shapeless
`mkSingletonOps` macro. Its expansion had the type of a freshly-named
class local to the expansion. Upon the re-expansion, a new class
was generated, which lead to errors like:
client/Client.scala:4: error: type mismatch;
found : fresh$macro$2
required: fresh$macro$1
This commit suppressed re-expansion of the expandee by use of
the existing, tree attachment driven mechanism.
|
|\
| |
| | |
Better error message than 'bad symbolic reference'.
|
| |
| |
| |
| |
| |
| | |
Let's not scare people, and try to give them some advice.
PS: we should really come up with a better mechanism for testing errors/warnings
|
|\ \
| | |
| | | |
Remove "throws InvalidEscapeException" from StringContext.raw doc
|
| | |
| | |
| | | |
As pointed out by @som-snytt, \u0023 is #, not \u0025.
|
| |/
| |
| | |
Since StringContext.raw doesn't escape its input, it does not call `treatEscapes` and cannot throw the InvalidEscapeException.
|
|\ \
| | |
| | | |
Remove invalidation from Global.scala
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The invalidation has been introduced in these commits:
https://github.com/scala/scala/commit/167309afd10f9b65b35e6874a30ea6340a1ddc44
https://github.com/scala/scala/commit/ace051ff0abe112b767c3912f846eb4d50e52cf5
https://github.com/scala/scala/commit/e156d4a7cf4afdab91b7c281a0e8ae6e4743cc4a
It's safe to remove this functionality. It was added originally to support an experiment with resident compilation. The experiment was performed in sbt and dropped in https://github.com/sbt/sbt/commit/6def08e029e474dc35af04b7403a2aeaddd0dec6
Since then Scala team concluded to not work on resident compilation so it's safe to delete unused code.
|
|\ \ \
| | | |
| | | | |
Assortiment of cleanups and comments around the backend
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
The final flag is computed correctly by javaFlags.
|
| | | | |
|
| | | | |
|
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The code that generated the Java varargs forwarder was basing
things on the `ValDef-s` of the parameters of the source method.
But, their types refer to a type parameter skolems of the enclosing
method, which led to a type mismatch when typechecking the forwarder.
Instead, I've reworked the code to simply use the `DefDef`-s symbol's
info, which *doesn't* refer to skolems. This actually simplifies the
surrounding code somewhat; rather than repeated symbols in a map
we can just time travel the pre-uncurry method signatures to figure
out which params are releated.
|
|\ \ \
| | | |
| | | | |
SI-8736 Restore -language to former glory
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Now `-language` with no option will emit an error:
```
$ skalac -feature -language unused.scala
scalac error: '-language' requires an option. See '-language:help'.
scalac -help gives more information
```
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
MultiChoice allows -language to work like -Xlint.
The bug as described was that the setting value was set instead of updated
(++=) with additional flags.
The unreported bug was that `_` no longer set all settings.
The corrected behavior is that "contains" means "it was enabled, or
_ was set and it was not disabled explicitly."
That is the behavior of `-Xlint` but with a different mechanism,
since each lint option is a Setting.
A semantic difference is that -Xlint enables all the lint options,
but -language does not enable all the language features. `scalac -X` does
not explain this additional behavior of the `-Xlint` flag.
Also worth noting that `scalac -feature -language unused.scala` failed
in 2.11.1 but succeeds silently now.
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
Missed the case of comparing a non-empty range to an empty one. Fixed by checking nonEmpty/isEmpty on other collection.
Added a test to verify the behavior.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Clean-up code review comments.
MultiChoice takes a helper function for outputting help text.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Enables -Xlint:help and -language:help.
The Settings API makes it difficult to innovate.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Also clarify usage of -Xlint flag.
Align more with javac -Xlint:all,-flag,flag where once a flag is
explicitly enabled it cannot be disabled, but where the wildcard
is a backstop only. (There is no all option yet here.)
-Xlint and -Xlint:_ just set a flag which is consulted by any
unset lint warning.
Xlint warnings consult the state of Xlint when they are unset.
Individual -Ywarn-ings do not.
Other warnings are explicitly set to false. They can only be
enabled programmatically.
Some tests are corrected. Also, option order is no longer
significant, see the unit test.
|
|\ \ \
| | | |
| | | | |
SI-8525 -Xlint:nowarn-missing-interpolator
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Turn anonymous references to `settings.lint` into named settings.
After that, trust to Adriaan to make them filterable.
There are a few remaining top-level -Y lint warnings that are
deprecated.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Turn off lint warnings with negating prefix, and add a lint-only
warning for the infamously nagging "Did you forget the interpolator?"
That message is made more dignified.
Without `-Xlint:false`, there is no mechanism to turn off
anonymous linters once `-Xlint` is selected.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is an error, not a crash.
Alternatively, one could define the multivalued colon case
as equivalent to specifying the option multiple times. That
would be very regular. But sometimes it's nicer just to error out.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Make -Xlint a "multichoice" option for purposes of option parsing.
This allows turning on "lint with these warnings" instead of only
"turn off these warnings but enable other lint warnings".
```
$ scalac -Xlint:warn-adapted-args linty.scala # lint plus a warning
$ scalac -Xlint warn-adapted-args linty.scala # same
$ scalac -Xlint linty.scala # same as now
$ scalac -Xlint -- linty.scala # ok, not necessary
$ scalac -Xlint _ -- linty.scala # another funky underscore
```
This would also enable Xlint options that are not standalone options,
although that is not implemented in this commit. For example,
`-Xlint:no-missing-interpolator` could be used to disable that
warning. (There is no `-Xoption:flavor=off` syntax.) (`no-` switches
would not be enabled by `_`.)
|
|\ \ \ \
| | | | |
| | | | | |
SI-8557 make scaladoc normalize paths of external jars.
|