Changelog for ineffassign-0.0.0+git20230610.0e73809-lp160.9.4.x86_64.rpm :

* Sat Aug 12 2023 jkowalczykAATTsuse.com- Update to version 0.0.0+git20230610.0e73809:
* A function is not deferred until after it and its args have been evaluated.
* Update issue templates
* Check length of builder.defers as maybePanic may be called outside of a function scope.
* Do not mark named function results as used if an operation might panic but will not be recovered (i.e., when there is no defer statement).
* Don\'t type-check the code being analyzed.
* Missed a spot.
* Don\'t treat nil initialization as assignment.
* doc: clarify meaning of ineffectual assignment- Use _service mode manual as better alias name than disabled
* Tue Mar 16 2021 Jeff Kowalczyk - Update to version 0.0.0+git20210225.2e10b26:
* Don\'t disregard operations that occur prior to a variable escaping.
* Move library code of the analyzer into pkg/ineffassign
* Extra \"is this file generated\" logic into func
* Ignore generated files.
* Adjust testdata comments to match what analysistest expects.
* Fix testdata compilation errors.
* Re-add support for -n flag (and run go fmt)
* Use analysis.Analyzer to implement ineffassign
* Update \"Usage\" in README
* Deprecate \"-n\" flag
* Add support for ... syntax for recursive analysis
* Ignore generated files
* Add docs on tool install and usage
* Terminate a block upon reaching a return statement.
* avoid repeating type assertions by switching on `x := x.(type)`
* Account for the pathological case where some clown redfined \'false\'
* Don\'t treat initialization to \'false\' as assignment.
* Packaging use go modules and vendor dependencies
* Packaging add obs-service-go_modules disabled
* Packaging drop BuildRequires: golang-packaging macros no longer used
* Packaging add rpmlintrc
* Fri Jan 04 2019 Jan Engelhardt - Use noun phrase in summary.
* Wed Jan 02 2019 ndasAATTsuse.de- enable tar_scm service
* Wed Jan 02 2019 opensuse-packagingAATTopensuse.org- 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
* Tue Jul 10 2018 mrosteckiAATTsuse.com- Initial release