scala/scala3 issues and pull requests

#24066 - Don't warn on private proxy extension idiom

Issue - State: open - Opened by som-snytt 2 months ago
Labels: itype:bug, area:linting, better-errors

#23835 - `[E008] Not Found Error:` fails due to clashing names, but doesn't mention it, nor provides suggestion on how to workaround

Issue - State: open - Opened by mr-git 3 months ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#23815 - Improve syntax error message for nested packaging missing braces

Issue - State: closed - Opened by som-snytt 3 months ago - 1 comment
Labels: itype:bug, area:parser, better-errors

#23693 - String iterpolation warnings should have a error id

Issue - State: closed - Opened by eejbyfeldt 4 months ago - 2 comments
Labels: itype:bug, area:reporting, better-errors

#23651 - multiple `@nowarn` annotation does not work since Scala 3.7.0

Issue - State: closed - Opened by xuwei-k 4 months ago - 6 comments
Labels: itype:bug, regression, better-errors

#23426 - Misleading leading infix error

Issue - State: open - Opened by som-snytt 6 months ago
Labels: itype:enhancement, better-errors

#23402 - Unhelpful type erasure error with multiple parameter groups

Issue - State: closed - Opened by threeseed 6 months ago - 10 comments
Labels: itype:enhancement, area:reporting, better-errors

#23350 - Unhelpful error message for type erasure

Issue - State: open - Opened by threeseed 6 months ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#23281 - wrong `you can simply leave out the trailing _` message

Issue - State: open - Opened by xuwei-k 6 months ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#23277 - Missing warning for Infinite recursive call in object

Issue - State: closed - Opened by drewfeelsblue 6 months ago - 3 comments
Labels: itype:enhancement, area:transform, better-errors

#23167 - value + is not a member of Int

Issue - State: open - Opened by scarf005 7 months ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#22997 - Improve error messages reporting overriding errors that involve refinements

Issue - State: open - Opened by kyouko-taiga 8 months ago
Labels: itype:enhancement, area:reporting, area:overloading, better-errors

#22969 - Unused warning for NotGiven is not useful

Issue - State: closed - Opened by eejbyfeldt 8 months ago - 3 comments
Labels: itype:enhancement, area:reporting, area:linting, better-errors

#22941 - Abstract error message only show the start of the name

Issue - State: closed - Opened by tgodzik 8 months ago - 3 comments
Labels: itype:bug, area:typer, area:positions, Spree, better-errors

#22903 - Unhelpful error message when using named patterns with custom selector type in extractor match

Issue - State: open - Opened by SrTobi 8 months ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#22832 - `@unroll` on a case class field without a default argument produces bad error message

Issue - State: open - Opened by lihaoyi 9 months ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#22785 - Unhelpful "This old given syntax is no longer supported" warning

Issue - State: open - Opened by slavaschmidt 9 months ago - 2 comments
Labels: itype:enhancement, area:reporting, better-errors

#22733 - False positive warning about passing implicits with a `using` clause in 3.7 nightly

Issue - State: closed - Opened by mrdziuban 9 months ago - 2 comments
Labels: itype:bug, stat:duplicate, area:implicits, better-errors

#22687 - Missing indent says `not a legal formal parameter for a function literal`

Issue - State: open - Opened by som-snytt 9 months ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#22623 - pattern selector should be an instance of Matchable when matching on Quotes Reflect API

Issue - State: closed - Opened by goshacodes 10 months ago - 3 comments
Labels: itype:enhancement, area:reporting, area:metaprogramming:quotes, better-errors, stat:fixed in next

#22615 - Misleading `Unreachable case` report in `ensuring`. Bug or feature?

Issue - State: open - Opened by martinberger 10 months ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#22607 - Bad error message when taking Tuple.IsMappedBy as evidence

Issue - State: open - Opened by eejbyfeldt 10 months ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#22567 - confusing `Implicit parameters should be provided with a using clause` message if implicit default param

Issue - State: closed - Opened by xuwei-k 10 months ago - 3 comments
Labels: itype:enhancement, area:reporting, better-errors

#22508 - Type not found in derived class when extending trait with inner class type projection

Issue - State: open - Opened by readren 10 months ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#22392 - `implicitNotFound` should allow type computation inside its pretty printer

Issue - State: open - Opened by belamenso 11 months ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#22333 - Type errors should evaluate type matches with known arguments

Issue - State: closed - Opened by belamenso 11 months ago - 3 comments
Labels: itype:enhancement, area:reporting, better-errors

#22197 - Parser should report ambiguous givens syntax

Issue - State: open - Opened by WojciechMazur 12 months ago
Labels: itype:enhancement, area:reporting, area:parser, better-errors

#22191 - `case' with `given' error has precedence over unreachable case

Issue - State: open - Opened by sjbiaga 12 months ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#22153 - Unactionable warning: "Given search preference for ... will change."

Issue - State: closed - Opened by eed3si9n about 1 year ago - 3 comments
Labels: itype:bug, area:reporting, better-errors

#21976 - Improve error messages for erroneous `export` statements

Issue - State: open - Opened by KacperFKorban about 1 year ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#21944 - Better error message when an enum extends AnyVal

Issue - State: closed - Opened by hamzaremmal about 1 year ago
Labels: itype:enhancement, area:reporting, area:desugar, area:enums, Spree, better-errors, area:value-classes

#21864 - False 'Pattern Match Exhaustivity' Warning

Issue - State: open - Opened by burak-yildirim about 1 year ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#21783 - Don't point to the compiler backlog when a compiler plugin phase crashes

Issue - State: closed - Opened by Gedochao about 1 year ago
Labels: itype:enhancement, area:reporting, better-errors, area:compiler-plugins

#21746 - very obfuscated error when using `val` in for comprehension

Issue - State: open - Opened by bishabosha about 1 year ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#21742 - pattern matching with given and vararg fails

Issue - State: open - Opened by sjbiaga about 1 year ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#21577 - Better warning for matching values with flexible types in explicit nulls

Issue - State: closed - Opened by noti0na1 about 1 year ago - 1 comment
Labels: itype:enhancement, area:reporting, area:nullability, good first issue, better-errors, area:private options

#21538 - Better error reporting is required for inlined non-immutable paths

Issue - State: closed - Opened by soronpo over 1 year ago - 5 comments
Labels: itype:enhancement, area:reporting, area:inline, Spree, better-errors

#21525 - false-positive "unused import" warning

Issue - State: closed - Opened by xuwei-k over 1 year ago - 2 comments
Labels: itype:bug, area:reporting, better-errors

#21365 - Unexpected warning when `@main` is used twice within a single object

Issue - State: closed - Opened by Gedochao over 1 year ago - 2 comments
Labels: itype:bug, area:annotations, area:reporting, Spree, better-errors

#21321 - (minor) usage of `scala.ContextFunction0` should produce "context function types require at least one parameter" error

Issue - State: closed - Opened by unkarjedy over 1 year ago
Labels: itype:bug, area:reporting, better-errors, area:context functions

#21282 - `-source:future-migration` generating warnings on `TypeRepr` matches

Issue - State: closed - Opened by kraktus over 1 year ago - 1 comment
Labels: itype:enhancement, area:reporting, area:metaprogramming:quotes, better-errors

#21240 - Union type: no warning for duplicate types

Issue - State: open - Opened by kraktus over 1 year ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#20946 - All `assert`s in `Quotes` should give helpful error messages

Issue - State: closed - Opened by KacperFKorban over 1 year ago
Labels: itype:enhancement, area:reporting, better-errors

#20741 - Incorrect "the type test for A cannot be checked at runtime because it's a local class" warning

Issue - State: open - Opened by uosis over 1 year ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#20651 - incorrect `Suspicious top-level unqualified call` warning message

Issue - State: open - Opened by xuwei-k over 1 year ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#20563 - No type-mismatch error in fewer-braces code when using context function

Pull Request - State: open - Opened by WojciechMazur over 1 year ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#20510 - Tell me if I try to define a companion to an existing symbol that is separately compiled

Issue - State: open - Opened by som-snytt over 1 year ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#20499 - Misleading unreachable case warning when matching on an inlined pattern matched type

Issue - State: open - Opened by DanielMoss over 1 year ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#20484 - Wrong warning emitted during implicit resolution

Issue - State: closed - Opened by hamzaremmal over 1 year ago - 2 comments
Labels: itype:enhancement, area:reporting, area:implicits, better-errors

#20462 - Error does not show why rewrite to assignment did not work out

Issue - State: open - Opened by som-snytt over 1 year ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#20414 - Strange cyclic reference errors in complex inheritance source with opaque types

Issue - State: open - Opened by OndrejSpanel over 1 year ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#20412 - Expected Warning not happening when using higher-kinded types

Issue - State: open - Opened by matheussbernardo over 1 year ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#20395 - Wrong unreachable code reported for inline def pattern match

Issue - State: closed - Opened by enif-lee over 1 year ago - 2 comments
Labels: itype:bug, area:pattern-matching, better-errors

#20338 - Wrong error message when using setter extension method with wrong type

Issue - State: closed - Opened by keynmol over 1 year ago - 3 comments
Labels: itype:enhancement, area:reporting, Spree, better-errors

#20266 - The match type contains an illegal case; what makes it illigal?

Issue - State: open - Opened by Adam-Vandervorst over 1 year ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

#20126 - Different error messages displayed on implicit parameter search failure for extensions on the extended type's singleton object vs outside

Issue - State: open - Opened by natsukagami over 1 year ago
Labels: itype:enhancement, area:reporting, stat:needs triage, better-errors

GitHub / scala/scala3 issues and pull requests