life
golangci-lint
life | golangci-lint | |
---|---|---|
1 | 72 | |
0 | 14,472 | |
- | 1.3% | |
10.0 | 9.7 | |
over 1 year ago | 5 days ago | |
Nim | Go | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
life
-
We Need To Talk About The Bad Sides of Go
Just as a small example, here is an sdl2 game of life thing that I made not so long ago: https://github.com/sotolf2/life/blob/main/life.nim so that you can get a little feel of the language, it might not be your cup of tea, but for me at least it just works very much how I think which is nice, flexible syntax and a really nice type system, nim is kind of like an anti-go :p Just negate most of the things go does and you have nim :p It's even cooler now when version 2 soon comes out where they got rid of the standard garbage collector, and use ORC instead, which at compiletime inserts allocs and frees, and only Reference count stuff that it detects as cycles, It's really cool, and really makes it come very close to C performance in most cases :)
golangci-lint
- makefile para projetos em Go
-
Finding unreachable functions with deadcode – The Go Programming Language
One of the checkers in golangci-lint does this. I forget which one.
golangci-lint rolls up lot of linters and checkers into a single binary.
There is a config file too.
https://github.com/golangci/golangci-lint
-
Using Private Go Modules with golangci-lint in GitHub Actions
golangci-lint is an amazing open-source tool for CI in Go projects. Basically, it's an aggregator and a Go linters runner that makes life easier for developers. It includes all the well-known liners by default but also provides an easy way to integrate new ones.
-
️👨🔧 3 Tiny Fixes You Can Make To Start Contributing to Any Open Source Project 🚀
Fun fact: We actually use a code linter via golangci-linter to catch misspellings in code/comments using client9/misspell.
-
Show HN: Error return traces for Go, inspired by Zig
The "standard linter" in Go is https://golangci-lint.run/ , which includes [1] the absolutely-vital errcheck which will do that for you.
For an Advent of Code challenge you may want to turn off a lot of other things, since the linter is broadly tuned for production, public code by default and you're creating burner code and don't care whether or not you have godoc comments for your functions, for instance. But I suggest using golangci-lint rather than errcheck directly because there's some other things you may find useful, like ineffassign, exportloopref, etc.
[1]: https://golangci-lint.run/usage/linters/
-
Hacking Go to give it sum types
golangci-lint recently integrated go-check-sumtype. I recommend using golangci-lint as a pre-commit hook, but if you're in a real hurry you can replace "go build" with a shell script that runs go-check-sumtype instead. This is probably better than a weird hack, not that you're saying that the weird hack is a good idea anyhow.
-
Building RESTful API with Hexagonal Architecture in Go
Golangci-lint is a tool for checking Go code quality, finding issues, bugs, and style problems. It helps keep the code clean and maintainable.
-
Structured Logging with Slog
This is such an infuriating problem. I'm convinced I'm using Go wrong, because I simply can't understand how this doesn't make it a toy language. Why the $expletive am I wasting 20-30 and more minutes per week of my life looking for the source of an error!?
Have you seen https://github.com/tomarrell/wrapcheck? It's a linter than does a fairly good job of warning when an error originates from an external package but hasn't been wrapped in your codebase to make it unique or stacktraced. It comes with https://github.com/golangci/golangci-lint and can even be made part of your in-editor LSP diagnostics.
But still, it's not perfect. And so I remain convinced that I'm misunderstanding something fundamental about the language because not being able to consistently find the source of an error is such an egregious failing for a programming language.
- golangci-lint 1.54.0 is released
- Seeking Insights: Tools Used in GitHub Actions for Security Code Checks and Vulnerability Detection
What are some alternatives?
bevy_snake - Clone of the snake game, with Bevy
ireturn - Accept Interfaces, Return Concrete Types
bevy - A refreshingly simple data-driven game engine built in Rust
gosec - Go security checker
golangci-lint-action - Official GitHub action for golangci-lint from its authors
gopl.io - Example programs from "The Go Programming Language"
go - The Go programming language
ls-lint - An extremely fast directory and filename linter - Bring some structure to your project filesystem
staticcheck
go-tools - Staticcheck - The advanced Go linter
golang-standards/project-layout - Standard Go Project Layout
maligned - Tool to detect Go structs that would take less memory if their fields were sorted.