Fix type test for trait parameter arguments #12064
Closed
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
The symbol might have original name in scope other than its current target name (after erasure).
Propagate visited set properly.
Fix detecting Scala3 version in useScaladoc
Deprecate sbt-dotty when using sbt >= 1.5.0-RC2
Fix scala#11731: Remove symbols with targetName correctly
Fix scala#11885: disable flaky idempotency test on Windows
Performance tweak for initialization check
…-RC2 Upgrade Dotty to 3.0.0-RC2
Fix broken script on Windows
```code @main def Test = val x = false val y = 1 val result = x || y.match case 1 => false case 3 => false case _ => true || !x assert(result) ``` In this code, the last `|| !x` was seen as a part of the previous case, so the code was parsed as ```scala @main def Test = val x = false val y = 1 val result = x || y.match case 1 => false case 3 => false case _ => true || !x assert(result) ``` This is highly surprising and unintuitive. The fix will insert an <outdent> token instead if the leading infix operator is too far to the left. Too far means: (1) left of the current indentation region, (2) and not to the right of any outer indentation widths. (2) allows to still parse code like this ```scala if xyz then one + two + three ``` Here, the width of the indentation region after `then` is 4, but the `+` operator is to the right of the outer indentation width of 0., so the indentation region is not closed. In other words, we do not close an indentation region if the result would not be legal, since it matches none of the previous indentation widths.
Fix derivedNames test on mac
Add 3.0.0-RC2 blog article
Fix scala#9871: use toNestedPairs in provablyDisjoint
Fix typo in idempotency test filter
CI: Automatically open an issue if nightly build fails
…erator Better handling of leading infix operators in indented code
Fix treatment of bottom types in OrType#join and baseType computations
Fix type NamedArg of annotations when pt is nullable
…izability" This reverts commit 60e3965.
The change was done accidentally.
Fix bug with doubling comments in Scaladoc
…c2-features Add handling for scaladoc 2 flags: private, groups, author, canonical doc url, project footer.
We cannot pull the try that catches the type error over both parts of `tryExtensionOrConversion` since a failed extension should still cause a conversion to be tried. We need to try both parts separately instead.
Better error message for errors arising from implicit completions
Allow by-name types in using clauses
- Concentrate everything in Checking -- it's too easy to add flag checking in several places otherwise. - Simplify some operations
Streamline flag checking
Revert "Recursively check nonvariant arguments of base types for realizability"
…aware-of-experiments Make community build docs experiment-aware
Bump to sbt 1.5.0
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.
Backport of #12041