kyoh86/exportloopref

Issues

• cannot detect case when exporting the address of a struct member

  #27 opened 8 months ago by ljw7630
  1

• add an explanation to README.md about Go 1.22

  #25 opened 9 months ago by mrwormhole
  1

• Forbid captured loop variables

  #22 opened 10 months ago by max-melentyev
  3

• False positive when a loop var is exported, directly followed by break

  #14 opened 10 months ago by alvaroaleman
  5

• possible false negative when assigning a new struct with loop variable to a local var

  #19 opened 10 months ago by Liooo
  7

• Is this still valid with per-iteration loop variables?

  #24 opened 10 months ago by andig
  2

• take sliced arrays into account

  #20 opened a year ago by kyoh86
  0

• No reports about using variable on range scope in function literal (deprecated `scopelint` finds it perfectly)

  #21 opened 2 years ago by mowtschan
  1

• Linter throwing Panic

  #13 opened 2 years ago by HirdrWit
  7

• fails to find out what scopelint does

  #12 opened 4 years ago by siddharth178
  7

• False positive when exporting a pointer to a loop variable field.

  #18 opened 3 years ago by joeblubaugh
  1

• False positive when ranging over a slice of pointers

  #2 opened 5 years ago by dgryski
  1

• Any benefits compared to gosec and scopelint

  #9 opened 5 years ago by georgysavva
  1

• Suggest fixes

  #7 opened 5 years ago by kyoh86
  0

• golangci-lint fails on exportloopref for go v1.13

  #8 opened 5 years ago by SVilgelm
  3

• exportloopref may be able to check decendants member like `a.b.c.d...`

  #5 opened 5 years ago by kyoh86
  0

• panic in checkUnaryExpr

  #3 opened 5 years ago by choleraehyq
  4