merge v2.13.8 tag to sbt-1.5 branch #5
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Inline Lifted.apply in condOpt
Fix Stream.iterator memory leak
Format typo in ClassfileAnnotation docs
The backend is now able to turn `x += 42` into an `iinc 42` instruction. The optimization only applies to `+=` and `-=`, provided the the net increment fits inside a signed 16-bit value (the ASM library handles choosing `iinc` or `wide iinc` as is appropriate). Fixes scala/bug#7452
Teach backend to emit `iinc` instructions
Yes, Option.get is bad and you should feel bad. But the deprecation warning should not give you such lessons, but just point to the replacement at hand.
In future, unapplySeq returning a Seq directly will be OK. For now, avoid confusion.
Accept supplementary Unicode characters in source code
Error on bad unapplySeq type
fix scala/bug#12420: complete LambdaType param symbols lazily
The deprecation was first proposed in scala#4990 but had been rejected because Scala.js did not support inline group names. Now that Scala.js 1.7.0 has been released with full inline group name support, there is no reason to perpetuate this API. Unfortunately, we cannot actually put `@deprecated` on the constructor of Regex with group names, since there is no alternative that does not take any group name. We *could* deprecate it anyway, with the replacement being to use `.r`, but perhaps that goes a bit too far.
Clean up junit test
…ups-api Deprecate ad hoc group names with Regex and .r
Improve unchecked type arg warnings
In scala#9558 (which shipped with 2.13.6) we added support for `case` bindings under -Xsource:3. Since this parser change does not break any existing code and since IntelliJ and scalameta/metals now understand this syntax in Scala 2 code, it should be safe to enable it by default to further ease cross-compilation between Scala 2 and 3.
- Specify the size when creating `ArrayBuffer`s - Modify intermediate results in place as much as possible - Don't allocate an `Option` for padding
Align doc and spec for Symbol
Non-specialized val fields in a specialized class are made non-final because of the way specialization is encoded. A `releaseFence` call is added to the constructor to ensure safe publication. The releaseFence call is not necessary for class parameters as those remain final. Follow-up for scala#9704, fixes scala/bug#12500
-Ypickle-write-java can generate Scala pickles for Java files. Unpickler needs to deal with the special case for Object/Any, as we do when using Java sources of javac compiled .class files as inputs. Fixes scala/bug#12512
Don't emit `releaseFence` for class params of specialized classes
When implicits are disabled, we can't recover later with a conversion. Esp. when we are already type checking an implicit conversion. This fixes a regression uncovered in Finch.
Deal with Object/Any impedence mismatch under -Ypickle-write-java
they are used only in the build and testing, but regardless, let's do it
upgrade sbt, logback, slf4j
Backport nowarn advice tweak
Tweak inferMethodInstance to consider if implicits are enabled
This reverts commit d047407. Reverts PR scala#9818; see scala/community-build#1519 for details on the community build failures
Revert PR scala#9818 (GroupedIterator improvements)
Scala 2.13.8
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
because sbt-1.5 seems to be the branch the Scala 3 community
build is using, at least at the moment. (after scala#9909
goes through we could start just using 2.13.x, I think)