Is golangci-lint Generics Readiness?

CIARANA — Thu, 23 Dec 2021 15:18:16 +0000

This post is Day 24 of Go Advent Calendar 2021(jp). 🎄🎅

golangci-lint is easy to use a very large of linters with a configuration file. On the other hand, it depends on a lot of linters, which makes it difficult to incorporate the latest implementations of them. Also, many of them have not been updated for some time. In such a situation, Go could introduce Generics at any moment. So I checked whether the linters support Generics or not, and summarized the results in the following list. In order to check if each linter supports or is going to support Generics, I search the issues and pull requests from the last 6 months using the keywords "generics", "type" and "1.18".

Name	Status	Remark
deadcode	⬜	no update for 5 years
errcheck	⬜	-
gosimple	⬜	-
govet	✅	https://tip.golang.org/doc/go1.18#vet
ineffassign	⬜	-
staticcheck	⬜	issue exists but not yet supported
structcheck	⬜	no update for 3 years（Reference to the package changed from GitHub to GitLab.）
typecheck	⬜	-
unused	⬜	-
varcheck	⬜	same as structcheck
asciicheck	⬜	-
bidichk	⬜	-
bodyclose	⬜	-
contextcheck	⬜	-
cyclop	⬜	-
depguard	⬜	-
dogsled	⬜	-
dupl	⬜	-
durationcheck	⬜	-
errchkjson	⬜	-
errname	⬜	-
errorlint	⬜	-
exhaustive	⬜	There is no indication of how it will be implemented, but there is an issue that talks about the need to update it.
exhaustivestruct	⬜	-
exportloopref	⬜	-
forbidigo	⬜	-
forcetypeassert	⬜	-
funlen	⬜	no update for a year
gci	⬜	-
gochecknoglobals	⬜	-
gochecknoinits	⬜	-
gocognit	⬜	-
goconst	⬜	-
gocritic	⬜	Previously fixed error is recurring.
gocyclo	⬜	-
godot	⬜	-
godox	⬜	issue tab is hidden
goerr113	⬜	-
gofmt	✅	Referencing standard packages via golangci/gofmt, so some may not be supported.
gofumpt	✅	https://github.com/mvdan/gofumpt/releases/tag/v0.2.0
goheader	⬜	-
goimports	✅	same as gofmt
golint	⬜	deprecated and archived
gomnd	⬜	-
gomoddirectives	⬜	-
gomodguard	⬜	-
goprintffuncname	⬜	no update for 2 years
gosec	⬜	-
ifshort	⬜	-
importas	⬜	-
interfacer	⬜	deprecated and archived
ireturn	⬜	-
lll	⬜	-
makezero	⬜	-
maligned	⬜	deprecated and archived
misspell	⬜	no update for 4 years
nakedret	⬜	-
nestif	⬜	-
nilerr	⬜	no update for a year
nilnil	⬜	-
nlreturn	⬜	-
noctx	⬜	-
nolintlint	⬜	-
paralleltest	⬜	-
prealloc	⬜	-
predeclared	⬜	-
promlinter	⬜	-
revive	⬜	-
rowserrcheck	⬜	-
scopelint	⬜	deprecated and archived
sqlclosecheck	⬜	-
stylecheck	⬜	-
tagliatelle	⬜	-
tenv	⬜	-
testpackage	⬜	-
thelper	⬜	-
tparallel	⬜	-
unconvert	⬜	no update for 2 years
unparam	⬜	There is an issue that states that `x/tools/go/ssa` supports Generics and then supports it.
varnamelen	⬜	-
wastedassign	⬜	https://github.com/sanposhiho/wastedassign/issues/41
whitespace	⬜	-
wrapcheck	✅	https://github.com/tomarrell/wrapcheck/commit/213318509af6a003be2be752da826d269149ba4d
wsl	⬜	-

Currently, most of the linters do not yet support Generics, and few of them have taken any action to support it. Even if the various linters support Generics, the latest golangci-lint will probably support it in due course. The reason for the lack of support may be that the official x/tools, including go/ssa, do not yet support Generics¹. Therefore, for production services that use golangci-lint regularly, it is better to experiment with Generics in the development environment only, and wait for a while before using it in the production environment. Conversely, it might be a chance to contribute them;)

There may be linters that do not fail with or without Generics. Also, some of them may actually support Generics due to my lack of confirmation, and some of them may support Generics after this post was published because I couldn't keep up with the latest information. In that case, please let me know in the comments.

https://github.com/golang/go/issues/48525 ↩

Quick Tutorial: Write Go, Run WASM!

CIARANA — Mon, 06 Aug 2018 16:01:07 +0000

Before Go 1.11 gets released, which introduces an experimental port to WebAssembly (WASM for short), I'm going to demonstrate how to compile Go source code into WASM and execute in the browser!

Here are the steps:

Setup go1.11beta3
Compile Go to WASM
Use HTML and JavaScript to load WASM
Spin up a web server
Open the website!

Step 1: Setup `go1.11beta3`

Although we need Go version 1.11 which is still in beta (due in August!), because Go is open-source we can just download the latest beta instead.

https://github.com/golang/go/releases/tag/go1.11beta3

$ go get golang.org/dl/go1.11beta3
$ go1.11beta3 download
# => Success. You may now run 'go1.11beta3'

Step 2: Compile Go to WASM

We can now write Go! The plan is to print the classic hello, Go/WASM! but in the browser––in the developer console.

// main.go
package main

import "fmt"

func main() {
    fmt.Println("hello, Go/WASM!")
}

To compile our program from Go to WASM, we use the command go build.

Note: We need to tell Go to compile for the web and not the default environment; our computer. So we need to set the environmental variables GOOS=js and GOARCH=wasm to target the web.

$ GOOS=js GOARCH=wasm go1.11beta3 build -o test.wasm main.go

Step 3: Use HTML and JavaScript to load WASM

This step isn't difficult; the Go team has prepared some files for us to experiment with.

# -s == silent mode
# -O == output mode
$ curl -sO https://raw.githubusercontent.com/golang/go/master/misc/wasm/wasm_exec.html
$ curl -sO https://raw.githubusercontent.com/golang/go/master/misc/wasm/wasm_exec.js

Step 4: Spin up a web server

Now we need to spin up a simple web server to serve some static assets. This is just a few lines of code:

// server.go
package main

import (
    "flag"
    "log"
    "net/http"
)

func main() {
    port := flag.String("port", "8000", "port")
    flag.Parse()
    log.Fatal(http.ListenAndServe(":"+*port, http.FileServer(http.Dir("."))))
}

Let's start it! Cheers!

$ go1.11beta3 run server.go

# or to run on a different port:
# $ go1.11beta3 run -port=8080 server.go

Step 5: Open the website!

Open localhost:8000/wasm_exec.html!

Note: A 'Run' button (at the top left) will appear disabled until the compiled WASM is loaded.

Once the 'Run' button is enabled, open the console and press the button!

See hello, Go/WASM!??

Congratulations! 🎉

You've just compiled, loaded, and run a Go program via WASM!

Is that true?

Why don't you confirm that Content-Type is application/wasm in the response header of test.wasm? ;)

Acknowledgements

Thank you ZAYDEK for recommending me to translate my article into English and reviewing this article.

DEV Community: CIARANA

Is golangci-lint Generics Readiness?

Quick Tutorial: Write Go, Run WASM!

Step 1: Setup `go1.11beta3`

Step 2: Compile Go to WASM

Step 3: Use HTML and JavaScript to load WASM

Step 4: Spin up a web server

Step 5: Open the website!

Acknowledgements

References

DEV Community: CIARANA

Is golangci-lint Generics Readiness?

Quick Tutorial: Write Go, Run WASM!

Step 1: Setup go1.11beta3

Step 2: Compile Go to WASM

Step 3: Use HTML and JavaScript to load WASM

Step 4: Spin up a web server

Step 5: Open the website!

Acknowledgements

References

Step 1: Setup `go1.11beta3`