Skip to content

devnev/go-lint-ref-after-nil-check

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

15 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Report uses of variables that are nil

When code has already dealt with a variable being nil, it doesn't usually make sense to continue referencing that variable. e.g.

func foo() error {
  result, err := DoSomething()
  if err != nil {
    return err
  }
  if result.IsBad() {
    return err
  }
  return nil
}

Usage

go get github.com/devnev/go-lint-ref-after-nil-check
go-lint-ref-after-nil-check source_file.go source_dir

Status

This has not been tested on a real codebase yet.

About

Lint for references to a variable after it has already been verified to be nil.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages