go-tools

Staticcheck - The advanced Go linter (by dominikh)

Go-tools Alternatives

Similar projects and alternatives to go-tools

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better go-tools alternative or higher similarity.

go-tools reviews and mentions

Posts with mentions or reviews of go-tools. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-07-27.
  • Ask HN: What are some interesting tools or code repos you discovered recently
    1 project | news.ycombinator.com | 25 Aug 2023
  • Gopher Pythonista #1: Moving From Python To Go
    3 projects | dev.to | 27 Jul 2023
    Another useful tool in Go is the go vet command, which helps to identify common coding mistakes such as unreachable code or useless comparisons. In addition, external linters like staticcheck can be used to detect bugs and performance issues with ease.
  • Find project-wide unused code using Golang's LSP
    2 projects | /r/golang | 23 May 2023
    For the last year or so (as of 2023) Golang has only had one active project for linting unused code, namely: unused from https://github.com/dominikh/go-tools. It works really well, but only within a package, not across packages, like within a traditional monolith. unused used to be part of another project called staticcheck, that did indeed have a flag for detecting project-wide unused code, but that is no longer supported. There are good reasons for that (see this Github discussion), mainly that it's computationally expensive.
  • Why tf golang let's you create maps with duplicated keys
    1 project | /r/golang | 4 May 2023
    To a degree, sure. It can't pick it up in general, because of the halting problem. But some trivial cases could be caught. Feel free to write such a linter, I'm sure Dominik would gladly merge it, for example.
  • Tools besides Go for a newbie
    36 projects | /r/golang | 26 Mar 2023
    IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here
  • New linter for mixing pointer and value method receivers
    2 projects | /r/golang | 30 Nov 2022
    Also proposal to staticcheck, will see if it goes through! https://github.com/dominikh/go-tools/issues/1337
  • this result of append is never used, except maybe in other appends (SA4010)
    1 project | /r/golang | 10 Nov 2022
    This is the first result for that error in google. The comment in that issue explains it. You're building two array's c_code, and c_start_date which are built and then never read or returned or otherwise used.
  • Zig, the Small Language
    13 projects | news.ycombinator.com | 7 Sep 2022
    This really irritated me when I started working with go, but it stopped bothering me and now I even mostly like it.

    The missing error checks are annoying, but if you have appropriate editor config it is hard to miss them: https://cdn.billmill.org/static/newsyctmp/warning.png

    Basically writing go without `staticcheck`[1] is not recommended. If you do have it set up, it's pretty easy to avoid simple errors like that.

    [1]: https://staticcheck.io/

  • Our experience upgrading from go v1.17 to v1.18 for generics
    2 projects | /r/golang | 20 Jul 2022
    However, recently [per this issue](https://github.com/dominikh/go-tools/issues/1270) it is safe to re-enable the ones I highlighted with strikethrough above. I would be interested in tracking issues for the remainder if you have those linked somewhere.
  • What are your strategies to prevent nil pointers errors in your code base?
    3 projects | /r/golang | 24 Jun 2022
    Unfortunately I don't know of any tools that can/do always detect it. There's this discussion for the staticcheck linter where they basically don't think it's worth false positives in order to support it a lint for it.
  • A note from our sponsor - InfluxDB
    www.influxdata.com | 19 Apr 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →

Stats

Basic go-tools repo stats
19
5,880
8.1
11 days ago
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com