go-sumtype
yaegi
go-sumtype | yaegi | |
---|---|---|
11 | 39 | |
403 | 6,609 | |
- | 1.1% | |
0.0 | 5.8 | |
about 1 year ago | 10 days ago | |
Go | Go | |
The Unlicense | Apache License 2.0 |
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.
go-sumtype
-
Small sum types in Golang
I find this implementation to be quite minimal and less clumsy than alternatives. Sure, you don't get nice exhaustive pattern matching. Also, type inference gets in the way when instantiating UserKey (though you can wrap it in constructor functions). But expressing your intent using types still makes your code much more convenient and easier to understand.
-
Switching from C++ to Rust
The call out to sum types is something I feel. I've been using Rust daily for almost 10 years now, and sum types are absolutely still one of the things I love most about it. It's easily one of the things I miss the most in other languages. I'm usually a proponent of "using languages as they're intended," but I missed exhaustiveness checking so much that I ported a version of it to Go[1] as a sort of lint.
[1]: https://github.com/BurntSushi/go-sumtype
-
Rusty enums in Go
A Google search for golang sum types currently shows my project as a second hit: https://github.com/BurntSushi/go-sumtype
-
Carbon Language: An experimental successor to C++
I've been writing Go and Rust nearly daily for about a decade now (Go is more than a decade, Rust is about 8 years). You are not going to teach me anything about the pros and cons of either language in a reddit comment. I do not need to be taught about the "iota mess" when I've written tooling for exhaustiveness checking in Go.
-
a go linter to check switch statements for default
https://github.com/BurntSushi/go-sumtype forces exhaustive type switches for interfaces specifically annotated to need that.
-
Go: Making state explicit using the type system
We can fix these two problems by relying on static analyzers such as go-sumtypes
-
Hacking sum types with Go generics
See also https://github.com/BurntSushi/go-sumtype
- What I'd like to see in Go 2.0
-
Upcoming Features in Go 1.18
go-sumtype[0] has completeness checking for sealed interfaces.
[0] https://github.com/BurntSushi/go-sumtype
-
I want enum more than generics
Pretty easy to achieve outside of the compiler: https://github.com/BurntSushi/go-sumtype
yaegi
- Traefik/Yaegi: Yaegi Is Another Elegant Go Interpreter
-
Go: What We Got Right, What We Got Wrong
Yes. There are long standing feature requests for (e.g.) the reflect package that simply don't get done because they'd break this assumption and/or force further indirection in hot paths to support "no code generation at runtime, ever".
Packages like Yaegi (that offers an interpreted Go REPL) have "know limitations, won't be addressed" also because of these assumptions.
https://github.com/golang/go/issues/4146
https://github.com/golang/go/issues/16522
https://github.com/traefik/yaegi?tab=readme-ov-file#limitati...
- Fourteen Years of Go
-
Gojekyll – 20x faster Go port of jekyll
There is always https://github.com/traefik/yaegi - a Go interpreter written to make it easy to write plugins.
- Jacobin: Minimal JVM written in Go and capable of running Java 17 classes
-
Can Go run statements in cmd like Python?
I think https://github.com/traefik/yaegi comes as close as using the python interpreter in you CLI, but for Go
-
Can Go files be compiled by themselves?
There's a go interpreter: https://github.com/traefik/yaegi It could run programs without compiling them, but there're some limitations.
-
referencing packages on the internet and using go plugin
I'd recommend looking into a different approach for plugins such as hashicorp/go-plugin (which uses multiple process PIDs and RPC communication between them) or traefik/yaegi (which implements a Go-compatible scripting language that can be interpreted at runtime and which still supports most Go modules).
-
Mun v0.4.0: a statically-typed scripting language like Rust, written in Rust
Why do we need a language like Rust when we have Rust. Why not just create a Rust interpreter. (There's such an interpreter for Go, BTW, https://github.com/traefik/yaegi )
-
Plugo - A plugin library for Go.
A cool solution I saw was Traefik's yaegi module. They basically created an interpreted scripting language with Go compatible syntax (turning Go into an interpreted, not compiled, language). I haven't tried this but it sounds like it brings the better parts of dynamic languages like Python's plugin support to Go - plugin writers can still write "Go" code, which can load dynamically.
What are some alternatives?
go101 - An up-to-date (unofficial) knowledge base for Go programming self learning
golive - ⚡ Live views for GoLang with reactive HTML over WebSockets 🔌
enumer - A Go tool to auto generate methods for your enums
gomacro - Interactive Go interpreter and debugger with REPL, Eval, generics and Lisp-like macros
go - The Go programming language
grule-rule-engine - Rule engine implementation in Golang
hylo - The Hylo programming language
gobook - Simple in Pure Go in Browser Interactive Interpreter
crubit
scriggo - The world’s most powerful template engine and Go embeddable interpreter
mo - 🦄 Monads and popular FP abstractions, powered by Go 1.18+ Generics (Option, Result, Either...)
gophernotes - The Go kernel for Jupyter notebooks and nteract.