6 ms·
I agree, but there's not much, and it's usually for decent reasons: * the "time" package hooks into the Go scheduler. * the "reflect" package needs type infor
by bradfitz 8y ago
I agree, but there's not much, and it's usually for decent reasons:
* the "time" package hooks into the Go scheduler.
* the "reflect" package needs type information out of the runtime.
* the "net" package hooks into the Go scheduler a bit. But way less than it used to. I think you might even be able to do this all yourself outside of std nowadays.
What else?
Our rough plan going forward is to actually move a bunch of the stdlib elsewhere but ship copies/caches of tagged versions with Go releases. So maybe "encoding/json" is really an alias for "golang.org/std/encoding/json" and Go 1.13.0 ships with version 1.13.0 of golang.org/std/encoding/json. But if you need a fix, feature, or optimization sooner than 6 months when 1.14.0 comes out, you can update earlier.
- aleksi 8y agoMy guess that quotemstr meant builtins: append, copy, range "protocol", etc.
- TheDong 8y agoThere are many examples of things builtins can do which user-code can't: 1. The constructs like "x <- chan" and "x, ok <- chan" (and map indexing and so on) are only available to builtin types. It's impossible to write a thing like "x, ok <- chan" where it either panics or doesn't depending on if the caller wanted two or one return values. 2. generic types, like 'map' and 'chan'. 3. 'len' can't be implemented for a user type, e.g. "len(myCustomWorkQueue)" doesn't work. 4. range working without going through weird hoops (like returning a channel and keeping a goroutine around to feed it) 5. Reserving large blocks of memory up front (e.g. as 'make' can do for slices and maps) in an efficient manner (e.g. make(myCustomWorkQueue, 0, 20) doesn't work)
- tptacek 8y agoYou're talking about the language. He's talking about the standard library.
- quotemstr 8y agoWe're both talking about both. The core of my complaint is that the language privileges parts of the standard library.
- TheDong 8y ago> privileges parts of the standard library It really doesn't. Maps and channels are not part of the stdlib. They're part of the language, but not the library. Similarly, range is part of the language, not the stdlib. If the stdlib was privileged, "container/*" in it would be generic, but it's not.
- quotemstr 8y agoAll right, but my point stands. Maps and channels should be part of stdlib, and they should rely on primitives available to user code too.
- tptacek 8y agoMaps and channels are not part of the standard library. How you know that is, you can replace the entire standard library, using none of it, and still be programming in Go with maps and channels.
- coldtea 8y agoParent wrote "should be" not "are".
- thefounder 8y agoSuch primitives would bring a lot of complexity which is something Go tried to avoid. Consider that make, map, chan etc are just language features/specs just like int64, string, func, main etc
- quotemstr 8y ago