| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Simplify the exposition and update the examples.
Emphasize pattern matching, especially using `r.unanchored`
instead of `for (r(x,y,z) <- r findFirstIn text)`.
Certain details are moved to method docs.
It would be nice to fix matching package doc,
but the doc must attach to the package object, it seems.
Introducing a package object is not binary-compatible.
Includes a doc line edit on 2.12, anticipating the merge.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Regex is robust when unapplying null. A null never matches.
|
|\ \ \ \ \ \
| |_|_|/ / /
|/| | | | | |
SI-8512 Infer a type for f"$args"
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Avoid the widening bug for q. This resolution also suffers
from the inference of Any, which can trigger a warning and
an anxiety attack. But that's still better than doing the
wrong thing.
Right?
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The f-interpolator gets a type param that better be Any to avoid
unfortunate widenings.
Hey, it worked!
Unfortunately, when `Any` is inferred, `-Xlint:infer-any` takes notice.
This is probably a greater problem for the f-interpolator than for
quasiquotes, which are a more specialized tool.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
test for InnerClass and EnclosingMethod attributes
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Some parts of the test assert (current) buggy behavior. This is marked
in the test file with TODO. It will be fixed in later work on the
backend.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
a few missing deprecations in proxy collections.
|
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | | |
SeqProxy was properly deprecated, so were the CollProxyLike classes, and
the ones in collection.immutable, but these four somehow survived
the Big Proxy Deprecation (tm).
|
|\ \ \ \ \
| | | | | |
| | | | | | |
SI-4563 friendlier behavior for Ctrl+D in the REPL
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Closing the REPL with Ctrl+D does not issue a newline, so the user's
prompt displays on the same line as the `scala>` prompt. This is bad.
We now force a newline before closing the interpreter, and display
`:quit` while we're at it so that people know how to exit the REPL
(since `exit` doesn't exist anymore).
The tricky part was to only add a newline when the console is
interrupted, and *not* when it is closed by a command (like `:quit`),
since commands are processed after their text (including newline) has
been sent to the console.
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
SI-6476 Improve error on escapement
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Strictly trivial updates for readability.
I used to prefer procedure syntax, but since it was
scheduled for removal, I can't scan a def without an
equals sign.
|
| | | | |
| | | | |
| | | | |
| | | | | |
And adjust the test.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Behavior of escape processing under string interpolation can
be confusing. This commit improves the exception message so
you know at least what sort of escapes are handled.
This came up on SO in the form `s"\d".r`, where it may not
be obvious what is throwing and how to work around it.
```
scala> s"\d".r
scala.StringContext$InvalidEscapeException: invalid escape '\d' not one of [\b, \t, \n, \f, \r, \\, \", \'] at index 0 in "\d". Use \\ for literal \.
scala> s"a\"
scala.StringContext$InvalidEscapeException: invalid escape at terminal index 1 in "a\". Use \\ for literal \.
```
Referencing SI-6476 because that has become the magnet ticket
for "escape processing under string interpolation, huh?"
This doesn't address `$"` and doesn't handle the more interesting
parse error `s"a\"b"`.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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)
|
|\ \ \ \
| | | | |
| | | | | |
Orphan check file
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
Orphaned by the override check reversion that deleted the test source.
2524fdde3edc7b668fdb4bf68e990141d3ec18d6
|
|\ \ \ \
| | | | |
| | | | | |
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.
|
|\ \ \ \
| |/ / /
|/| | | |
SI-8781 Avoid double-expansion under -Ymacro-expand:discard
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
|\ \ \
| | | |
| | | | |
Also update jline.version when update.versions is set during build
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
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
|
|\ \ \ \
| | | | |
| | | | | |
Bump versions for Scala 2.11.2
|
| |/ / / |
|
|\ \ \ \
| | | | |
| | | | | |
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
|