ineffassign
Detect ineffectual assignments in Go code
- Devel package for openSUSE:Factory
-
1
derived packages
- Links to openSUSE:Factory / ineffassign
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:languages:go/ineffassign && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
_service | 0000000628 628 Bytes | |
_servicedata | 0000000240 240 Bytes | |
ineffassign-0.0.0+git20180909.1003c8b.tar.xz | 0000007828 7.64 KB | |
ineffassign.changes | 0000001116 1.09 KB | |
ineffassign.spec | 0000001840 1.8 KB |
Revision 2 (latest revision is 9)
Michał Rostecki (mrostecki)
accepted
request 662552
from
Nirmoy Das (ndas)
(revision 2)
- enable tar_scm service - Update to version 0.0.0+git20180909.1003c8b: * Don't treat initialization to zero like `x := int64(0)` as assignment. * Guard against invalid code (break/continue outside of loop). * Definitely don't panic in maybePanic. * Mark named function results as used in operations that may panic. * Don't treat explicit initialization to zero as assignment; it is often used as shorthand for a bare declaration. * Support multiple path arguments on the command line. * Add a note to the README about limitations. * Slicing an array or taking the address of an array element causes the array to escape. * Use control flow analysis to find more useless assignments. * ignore vendor directories
Comments 0