SI-7620 Remove floating-point-literals-without-digit-after-dot
makes it more convenient to work with SuppressMacroExpansionAttachment
SI-7265 General test for spec version

The test for isJavaAtLeast uses the specification.version.

The method argument must have the form "major.minor".

The scaladoc is updated to reflect the new reality and a
test is added under junit.

Note that this implementation aims to be a simple
compromise between the functional and imperative camps,
that is, to be free of both closures and while loops.
And to elicit no cruft like regexes and wrappers for strings.
No doubt even more could be done in this department, but we
don't wish to spoil the fun on codegolf.stackexchange.com.
However, we might decide to sponsor a new site:
codereviewpingpong.com

For 2.10.x, javaSpecVersion is provided as a private member.
The active test is under `run` and the `junit` test must
bide its time in `pending`.

For 2.11, the private members can be public and the app test
replaced with the unit test.
SI-7336 - Link flatMapped promises to avoid memory leaks
SI-7638 Superaccessor lookup after specialization

The crash was caused by a symbol lookup to rewire the super calls,
done after pickler, but specialization added new traits and new
members, thus making the super rewiring impossible. To avoid such
problems, this patch moves symbol lookup after specialization,
so the changes done by specialization (and miniboxing) become
visible to mixin.

NOTE: This patch will be followed by a similar patch to master.

Review by @adriaanm or @retronym.
fix typo in BigInt/BigDecimal deprecation messages
SI-7617 typedAssign no longer expands lhs

This makes sure that setter and updateDynamic macros work as intended
rather than in some cases expanding incorrectly or prematurely.

Setter invocations are desugared from assignments of values to getters.
If a typecheck of an assignment's lhs yields an invocation of a getter,
then the assignment is rewritten into an invocation of a setter. However
if a getter is a macro, then it just expands, destroying the prerequisite
for desugaring. Therefore we need to disable expansion for the typecheck
of an lhs.

Similar thing happens to updateDynamic that first desugars a getter
invocation into q"$target.updateDynamic($fieldName)" and then expects
typedAssign to rewrite the corresponding Assign node into an additional
application of a partially applied updateDynamic to a rhs. Here we also
need to disable the typecheck of an lhs, because macros cannot be
partially applied.
SI-7649 Fix positions for reshaped tag materializers

Calls to `materializeClassTag[T]` are replaced during reification with
`implicitly[ClassTag[T]]` in the `reify` macro. This is done to avoid
referring to symbols in scala-compiler.jar. Class- and Type-Tag
materialization is treated in the same way.

This commit positions the replacement trees to avoid triggering
assertions under -Yrangepos.
Merge pull request #2712 from VladUreche/issue/7638

SI-7638 Superaccessor lookup after specialization
Merge pull request #2689 from scalamacros/ticket/7617

 SI-7617 typedAssign no longer expands lhs
Merge pull request #2716 from SethTisue/terribly-important-typo-fix

fix typo in BigInt/BigDecimal deprecation messages
Merge pull request #2721 from retronym/ticket/7649

SI-7649 Fix positions for reshaped tag materializers
Merge pull request #2666 from som-snytt/issue/7265-spec-at-least

SI-7265 General test for spec version
Merge pull request #2674 from richdougherty/2.10.x-si7336-try2

SI-7336 Link flatMapped promises to avoid memory leaks
SI-7657 clarifies the "macro overrides method" rule

Currently we allow macros to override non-abstract methods (in order
to provide performance enhancements such as foreach for collections),
and we also disallow macros to override abstract methods (otherwise
downcasting might lead to AbstractMethodErrors).

This patch fixes an oversight in the disallowing rule that prohibited
macros from overriding a concrete method if that concrete method itself
overrides an abstract method. RefCheck entertains all overriding pairs,
not only the immediate ones, so the disallowing rule was triggered.

Now macros can override abstract methods if and only if either the base
type or the self type contain a matching non-abstract method.
SI-7636 Fix a NPE in typing class constructors

If we encountered an erroneous super call due to a
failure in parent type argument inference, we must
avoid inspecting the untyped children of erroneous
trees.
SI-7668 Better return type inheritance for dep. method types

Return type inheritance already handles substitution of
type parameters of the overriding method for those of the
overriding.

This commit extends this to do the same for parameter symbols.
SI-7669 Fix exhaustivity warnings for recursive ADTs.

The pattern matcher's analysis was correctly finding
models under which the match in the enclosed test
could fail. But, when trying to render that model
as a counter example, it ran into an internal inconsistency
and gave up.

That inconsistency arose from VariableAssignment, which:

> turn the variable assignments into a tree
> the root is the scrutinee (x1), edges are labelled
> by the fields that are assigned a node is a variable
> example (which is later turned into a counter example)

In the process, it notes the unreachable case `V2 = NotHandled`,
which can only arise if `V1 = Op`, ie the scrutinee is `Op(NotHandled())`.
V2 is assosicated with the path `x1.arg`. The code then looked for
any variable assosicated with the prefix `x1` and registered that its
field `arg` was assosicated with this variable assignment.

However, the assignment for `V1 = NotHandled` (another missing case)
is also associated with the path `x1`. Registering this field makes
no sense here; we should only do that for `Op`.

This commit conditionally registers the fields based on the class
of `VariableAssignment#cls`. We no longer hit the inconsistency in
`VariableAssignment#allFieldAssignmentsLegal`.

This favourably changes the results of two existing tests.

I had to tweak the counter example pruning to avoid relying on
CounterExample.==, which is flaky in the light of Nil and List().
It is possible to have:

     A, B where A != B && A.coveredBy(B) && B.coveredBy(A)

Luckily it is straightforward to implement pruning entirely with
coveredBy.
Cleanups in type printing.

More consistency as to how to understand aliases,
singletons, specialized symbols, subclasses. Fewer
weird special casings, like normalizing tuples
and functions during type printing, but nothing else.
I avoid "normalize" entirely now, and do not make
special cases for dealiasing, which is already well
handled when printing error messages.

Look at the change to test/files/neg/t2641.check to get
a sense of why we should resist calling normalize during
the early days of a compilation run.

Anonymous and refinement classes can be printed far more
usefully by revealing their parents, and that too is here.

Hardened toString against undesirable side effects.
Make toString final to discourage any further rogue
toString overriders. Make safeToString a little safer.
Make -Ytyper-debug output readable.