MicroSCOPE
go
| MicroSCOPE | go | |
|---|---|---|
| 3 | 2,184 | |
| 15 | 124,539 | |
| - | 0.5% | |
| 3.8 | 10.0 | |
| 11 months ago | about 17 hours ago | |
| Go | Go | |
| BSD 3-clause "New" or "Revised" License | BSD 3-clause "New" or "Revised" License |
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.
MicroSCOPE
go
- Go proposal: finite type set interface as union type
-
Good union types in Go would probably need types without a zero value
// handle unexported go stdlib error, XXX fix after https://github.com/golang/go/issues/35234
-
Weak pointers in Go: why they matter now
Go without concurrency is fully memory safe. However, once you start using goroutines there can be memory corruption and segfaults: https://github.com/golang/go/issues/37484. Note that these are not recoverable panics (such as "writing to a close channel"), but causes completely arbitrary behavior:
runtime: pointer 0xc00379ac60 to unused region of span span.base()=0xc001794000 span.limit=0xc001795e00 span.state=1 -
Union types ('enum types') would be complicated in Go
As for first entry, this has been discussed many times without ever reaching any consensus, see - https://github.com/golang/go/issues/19412
- Glojure: Clojure interpreter hosted on Go, with extensible interop support
- How Much Memory Do You Need in 2024 to Run 1M Concurrent Tasks?
-
Hyrum's Law in Golang
To be fair to those projects, the type was introduced only three years ago:
https://github.com/golang/go/pull/49359/files
Before that, doing a string compare was basically the only way to detect that specific error. That was definitely an omission on the part of the original authors of the stdlib code; I don't it should be classified as "Hyrum's Law".
-
Build Golang from Source for v1.23+
git clone https://github.com/golang/go OR git clone https://go.googlesource.com/go
-
Personal TODO list on how I set up my dev machine
I install go.
-
Constraints in Go
The difference between types.Implements and types.Satisfies is mainly a history reason, a tradeoff between keeping backward compatibility and theory perfection.
It is pity that Go didn't support the "comparable" interface from the beginning. If it has been supported since Go 1.0, then this tradeoff can be avoided.
There are more limitations in current Go custom generics, much of them could be removed when this proposal (https://github.com/golang/go/issues/70128) is done.
I recommend people to read Go Generics 101 (https://go101.org/generics/101.html, author here) for a thoroughly understanding the status quo of Go custom generics.