-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Issues: scala/scala3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Extractor returning Issues tied to the named tuples feature.
area:pattern-matching
area:reporting
Error reporting including formatting, implicit suggestions, etc
itype:bug
NamedTuple is not considered exhaustive
area:named-tuples
#23158
opened May 14, 2025 by
eejbyfeldt
Compiler crash returning Issues tied to the named tuples feature.
area:pattern-matching
itype:bug
itype:crash
Some[NamedTuple in extractor
area:named-tuples
#23155
opened May 14, 2025 by
eejbyfeldt
"Unreachable case" is, in fact, reachable
area:pattern-matching
area:reporting
Error reporting including formatting, implicit suggestions, etc
better-errors
Issues concerned with improving confusing/unhelpful diagnostic messages
itype:bug
#23113
opened May 7, 2025 by
durban
Unclear warning in pattern match
area:pattern-matching
area:reporting
Error reporting including formatting, implicit suggestions, etc
itype:bug
#23028
opened Apr 22, 2025 by
tgodzik
Poor code generated for non-failing pattern match
area:pattern-matching
itype:enhancement
#23016
opened Apr 18, 2025 by
nmichael44
no warn when pattern match not exhaustive
area:pattern-matching
area:reporting
Error reporting including formatting, implicit suggestions, etc
itype:bug
#23006
opened Apr 16, 2025 by
road21
Variance does not play well with pattern matching
area:pattern-matching
area:variance
Issues related to covariance & contravariance.
itype:bug
#22993
opened Apr 12, 2025 by
TomasMikula
Failure to refine @-bound variables (x @ <pattern>) when pattern is a literal
area:pattern-matching
itype:bug
#22954
opened Apr 9, 2025 by
TomasMikula
Lost non-exhaustivity and unreachability warning for union of singletons resulting from match type returned from a method
area:pattern-matching
area:reporting
Error reporting including formatting, implicit suggestions, etc
itype:bug
#22952
opened Apr 9, 2025 by
TomasMikula
Improve error: the pattern contains an unaccounted type parameter
area:match-types
area:pattern-matching
area:typeclass-derivation
better-errors
Issues concerned with improving confusing/unhelpful diagnostic messages
itype:bug
#22943
opened Apr 8, 2025 by
TomasMikula
Unhelpful error message when using named patterns with custom selector type in extractor match
area:pattern-matching
area:reporting
Error reporting including formatting, implicit suggestions, etc
better-errors
Issues concerned with improving confusing/unhelpful diagnostic messages
itype:enhancement
#22903
opened Apr 1, 2025 by
SrTobi
Pattern matching value
s against a literal does not refine s.type to that literal
area:pattern-matching
itype:bug
#22887
opened Mar 28, 2025 by
TomasMikula
Changed type constraint behaviour when pattern matching with unions
area:pattern-matching
area:typer
itype:bug
regression
This worked in a previous version but doesn't anymore
#22882
opened Mar 28, 2025 by
WojciechMazur
Named tuple selector type in match means no exhaustivity
area:named-tuples
Issues tied to the named tuples feature.
area:pattern-matching
itype:bug
#22810
opened Mar 15, 2025 by
som-snytt
Implementation of SIP-67: better pattern matching with scala.language.strictEquality
itype:language enhancement
strictEquality
area:pattern-matching
area:strictEquality
#22732
opened Mar 6, 2025 by
mberndt123
Misleading Error reporting including formatting, implicit suggestions, etc
better-errors
Issues concerned with improving confusing/unhelpful diagnostic messages
itype:enhancement
stat:cannot reproduce
stat:needs minimization
Needs a self contained minimization
Unreachable case report in ensuring. Bug or feature?
area:pattern-matching
area:reporting
#22615
opened Feb 16, 2025 by
martinberger
Scala 3.6.3: pattern matching abstract types is broken in presence of ClassTag
area:pattern-matching
itype:bug
itype:soundness
Soundness bug (it lets us compile code that crashes at runtime with a ClassCastException)
#22547
opened Feb 6, 2025 by
arturaz
Incorrect exhaustivity warning when using opaque types with constraint and enums
area:enums
area:opaque-types
area:pattern-matching
area:reporting
Error reporting including formatting, implicit suggestions, etc
itype:bug
#22513
opened Feb 4, 2025 by
eejbyfeldt
False exhaustivity warning when unapply return type is a tuple defined using *:
area:pattern-matching
itype:bug
#22355
opened Jan 13, 2025 by
eejbyfeldt
Pattern Matching inconsistency
area:pattern-matching
area:reporting
Error reporting including formatting, implicit suggestions, etc
itype:bug
#22064
opened Dec 2, 2024 by
CyrilFMoser
Unreachable case false-positive for type-parametered boolean extractors
area:pattern-matching
itype:bug
#21829
opened Oct 22, 2024 by
ivan-klass
Inconsistent space analysis when singleton types are nested in
And/Or types
area:pattern-matching
itype:bug
#21723
opened Oct 7, 2024 by
noti0na1
Pattern matching against Linting warnings enabled with -W or -Xlint
area:pattern-matching
itype:bug
enum case without parameters compiles without warnings
area:linting
#21618
opened Sep 19, 2024 by
lolgab
Explicit type specification in
match worsens type checks
area:pattern-matching
itype:bug
#20705
opened Jun 20, 2024 by
mohe2015
Wrong unreachable code reported for inline def pattern match
area:pattern-matching
better-errors
Issues concerned with improving confusing/unhelpful diagnostic messages
itype:bug
#20395
opened May 13, 2024 by
enif-lee
Previous Next
ProTip!
Follow long discussions with comments:>50.