exhaustive VS gopherjs

This is an analyzer that will catch this: https://github.com/nishanths/exhaustive

I believe it's in golangci-lint.

I agree linters in general are quite useful for Go though. The default suite from golangci-lint is quite good. I would also recommend enabling exhaustive if you're working with a codebase that uses "enums" (full disclosure, I contributed a bit to that project).

there’s a linter for exhaustive matching: https://github.com/nishanths/exhaustive

I tried to find that linter and found this: exhaustive

And in Go you'd use a linter, like this one.

this is AST go vet analyzer that performs just that: https://github.com/nishanths/exhaustive (too bad it can not do struct based enums..)

>> the main thing missing from Go is ADT's. After using these in Rust and Swift, a programming language doesn't really feel complete without them

What are the differences between an ADT (plus pattern matching i’d reckon?) in Rust/Swift vs the equiv in Go (tagged interfaces + switch statement)?

One has exhaustive matching at compile time, the other has a default clause (non exhaustive matching), although there’s an important nub here with respect to developer experience; it would be idiomatic in Go to use static analysis tooling (e.g. Rob Pike is on record saying that various checks - inc this one - don’t belong in the compiler and should live in go vet). I’ve been playing with Go in a side project and using golint-ci which invokes https://github.com/nishanths/exhaustive - net result, in both go and rust, i get a red line of text annotated at the switch in vscode if i miss a case.

Taking a step back, there isn’t a problem you can solve with one that you can’t solve with the other, or is there?

To take a step further back, why incomplete?

Use a linter.

For an exhaustive linter, were you referring to this? It looks pretty nice. If it's possible to check this with static analysis, is it something that could be in the compiler itself in the future?

https://github.com/nishanths/exhaustive

here, have fun. You’re gonna write some tests, make new types to satisfy interfaces for testing, and then wind up with branches for your test paths in your live code, but go for it, I guess. You know everything! I am but a simple blubbite, too dim, too dim to get it.

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

Release notes have all the details. For now it is just compatibility with the 1.18 standard library, but generics support is planned.

Why not use https://github.com/gopherjs/gopherjs with jMonkeyEngine as-is?

When I wrote my first project in this year, I don't even planed to used blazor. But my childlike curiosity directed me on that path. I wanted to know, haw hard will be port game from desktop to web browser in .net. And I found out is not that hard. But I have experience with similar tools before. I used gopherjs and emscripten. Thanks to that I know what must to do, to communicate c# with javasrcipt. I made working blazor port pretty fast. Not only server side but webassembly to. Of curs create port for different platform always generate some problems. Most weird problem I have in blazor is how floating point number behave. I received in some cases NaN values. This problem I resolve adding value like 0.0001 in calculation.

If you're already building the backend in go and you don't like the prospect of coding in JavaScript it might be worth trying out https://github.com/gopherjs/gopherjs

Maybe this is were https://github.com/gopherjs/gopherjs will truly shine? Has anyone ever seen Go used for this?

You can also write JS in Go with GopherJS, but if you don't fully understand the underlying JS webdev ecosystem, adding this extra layer of complexity is probably a really bad idea, at least at first.