nishanths/exhaustive

Issues

• Feature Request: Allow specifying that a type isn't an enum

  #76 opened 7 months ago by iwahbe
  2

• go test ./... takes 35–45 seconds to complete

  #75 opened 9 months ago by nishanths
  0

• define behavior when both "ignore" and "enforce" comment is present on the same switch/map statement

  #49 opened 9 months ago by nishanths
  1

• stricter requirements for directive comments

  #70 opened 9 months ago by nishanths
  0

• `info.Defs[%s] == nil` panic when `go.mod` have `go 1.22`

  #73 opened 9 months ago by Gyllsdorff
  2

• feature: check exhaustiveness of type switches for sealed interfaces

  #74 opened 9 months ago by dkrieger
  0

• borrow possibly useful ideas from swift's TypeCheckSwitchStmt.cpp file

  #71 opened a year ago by nishanths
  0

• add docs for -default-case-required flag, related directive comments

  #69 opened a year ago by nishanths
  0

• Check exhaustiveness of map values in addition to keys

  #66 opened a year ago by dillonstreator
  2

• request a new option enforce-enum-types

  #65 opened a year ago by fatsheep9146
  5

• support for reading "-ignore-enum-types" and "-ignore-enum-members" values from files

  #57 opened a year ago by nishanths
  1

• Report invalid enforcement comments

  #59 opened 2 years ago by ImprintNav
  2

• Doesn't detect iota enums without type annotation

  #62 opened a year ago by yaseenkadir
  1

• Allow exhaustive check on map enum values as well as keys

  #58 opened 2 years ago by ImprintNav
  1

• Check enum based on struct

  #33 opened 3 years ago by maratori
  4

• Allow exhaustiveness checks on structs

  #40 opened 2 years ago by FastNav
  2

• report ineffectual ignore comments

  #52 opened 2 years ago by nishanths
  1

• hardcoded ignore list of certain std lib types that can never be enum types

  #34 opened 2 years ago by nishanths
  1

• option to ignore switch statements on things like reflect.Kind

  #51 opened 2 years ago by TristanSpeakEasy
  5

• superfluous type conversion in case clause results in a false positive report

  #42 opened 2 years ago by nishanths
  1

• missing diagnostics for switch statements that switch on a value whose type is a type parameter

  #31 opened 2 years ago by nishanths
  3

• Validate `map` keys the same way as `switch` cases

  #35 opened 2 years ago by maratori
  9

• in printed diagnostic, sort the missing constant names by AST order (not lexicographical order)

  #41 opened 2 years ago by nishanths
  0

• Allow explicit allowlist mode for switch-case checking

  #36 opened 3 years ago by FastNav
  3

• Analyzer incorrectly detects comment directives on nested switch statements

  #37 opened 3 years ago by FastNav
  1

• False positive if dot import is used

  #32 opened 3 years ago by maratori
  1

• define/implement exhaustiveness checking of type-aliased enums

  #13 opened 3 years ago by nishanths
  6

• analyzeCaseClauseExpr may not correctly handle "." import enum members in case clause

  #27 opened 3 years ago by nishanths
  0

• import a complex package such as "os" in testdata files

  #25 opened 3 years ago by nishanths
  0

• support exhaustiveness checks for non package-level enum types (e.g. enum types defined inside a function)

  #11 opened 3 years ago by nishanths
  1

• same name enum type in inner scope can produce incorrect diagnostic

  #23 opened 3 years ago by nishanths
  0

• bug: duplicate case is reported

  #3 opened 4 years ago by flisky
  4

• panics with reverted switch + external package

  #15 opened 3 years ago by antonio-antuan
  5

• add support for new flags to golangci-lint

  #20 opened 3 years ago by nishanths
  1

• rename and deprecate '-ignore-pattern' flag

  #14 opened 3 years ago by nishanths
  3

• switch the project's CI to GitHub's built-in CI

  #16 opened 3 years ago by nishanths
  1

• consider making the '-fix' flag a no-op

  #18 opened 3 years ago by nishanths
  1

• refactor into unit-testable functions, write unit tests

  #12 opened 3 years ago by nishanths
  3

• Support type aliasing

  #7 opened 3 years ago by Antonboom
  5

• Panic in latest release

  #10 opened 3 years ago by angadn
  3

• provide a way to exclude *_UNSPECIFIED generated for protobuf enums

  #8 opened 3 years ago by powerman
  2

• What if I have include some cases in default?

  #6 opened 4 years ago by mooxiu
  2

• "_" should be excluded

  #2 opened 4 years ago by sni
  3

• handle "default" case

  #1 opened 4 years ago by dcu
  1