0xjnml

7 ms·

31.
Tk9.0: The CGo-free, cross platform GUI toolkit for Go(pkg.go.dev)
7 points by 0xjnml 2y ago|0 comments
32.
by 0xjnml 2y ago
Except AI was correct this time. "It is rare to Close a DB, as the DB handle is meant to be long-lived and shared between many goroutines." source: https://pkg.go.dev/database/sql#DB.Close
33.
by 0xjnml 2y ago
> This would be much harder to do with modernc. https://go.dev/play/p/IztwH9Jl68i
34.
by 0xjnml 2y ago
Another simple WAL: https://pkg.go.dev/modernc.org/file#WAL
35.
Golang: Concurrent JavaScript and Go Channels(pkg.go.dev)
1 points by 0xjnml 2y ago|0 comments
36.
modernc.org/sqlite now supports Linux/loong64(pkg.go.dev)
1 points by 0xjnml 2y ago|0 comments
37.
by 0xjnml 3y ago
Go does not have enum types and Go does not have [Pascal-style] subrange types. The correct title should read "Go named constants suck", but then I'm not sure what's wrong about them.
38.
by 0xjnml 3y ago
Go enums cannot suck because Go has no enum types, full stop.
39.
by 0xjnml 3y ago
> https://github.com/golang-standards/project-layout The name of the repo is really and intentionally misleading. rsc filled an issue there to point this out, but the repo maintainer just disabled issues altogether
40.
by 0xjnml 3y ago
See https://go.dev/doc/modules/layout (Note: Even there the word 'standard' does not apear at all.)
41.
Golang: Toy Go compiler in < 200 SLOC(pkg.go.dev)
3 points by 0xjnml 3y ago|1 comments
42.
by 0xjnml 3y ago
Go0 is a [self] educational toy Go compiler for a minimalistic subset of Go. It demonstrates how to use the modernc.org/libqbe compiler back end.
43.
Libqbe for Go(pkg.go.dev)
1 points by 0xjnml 3y ago|1 comments
44.
by 0xjnml 3y ago
Package libqbe is a compiler backend. It compiles SSA source code to assembler source code.
45.
by 0xjnml 3y ago
$ mkdir foo $ cd foo $ go mod init example.com/foo $ touch foo.go
46.
by 0xjnml 3y ago
tl;dr: Looking forward future Pinner.Pinn performance improvements.
47.
by 0xjnml 3y ago
The Go code shown now is both syntactically valid and semantically correct: https://go.dev/play/p/GDki9v78jMM I can't check how it looked 15 hours ago. Makes me wonder if it was manually corrected and is thus
48.
Producing a Go scanner in 1219 bytes of code(modern-c.blogspot.com)
2 points by 0xjnml 3y ago|0 comments
49.
by 0xjnml 4y ago
C is a very common letter. That's why people search for it using the word clang. Oh wait.
50.
by 0xjnml 4y ago
openbsd/amd64 is not a supported target. Here's the list: https://pkg.go.dev/modernc.org/sqlite#hdr-Supported_platform...
51.
Go stdlib regexp package: A DFA experiment(gitlab.com)
2 points by 0xjnml 4y ago|1 comments
52.
by 0xjnml 4y ago
modernc.org/regexp @v1.2.0, relative to the stdlib regexp package: - performance sec/op, geomean -14.51% - throughput B/s, geomean +25.99% - regexredux-dna, wall time: -63.4%
53.
by 0xjnml 4y ago
> The gist is Go ignores all research in programming languages. This is an assumption and it's IMHO false. Go creators watched all the research, probably closely, lived with its results and were not happy with what they get. Their e
54.
by 0xjnml 4y ago
From the language specification: "The iteration order over maps is not specified and is not guaranteed to be the same from one iteration to the next." There's a long shot between "not specified" and "uniformly
55.
by 0xjnml 4y ago
All commits to the Go repository must be approved by two Google employees: https://groups.google.com/g/golang-dev/c/K7oGURi0wTM/m/3mg1O...
56.
by 0xjnml 4y ago
Thanks for the feedback, I tried to add a paragraph explaining it a bit more. Please let me know if it did not help, thanks.
57.
Producing a Go parser from the language specification mechanically, mostly(modern-c.blogspot.com)
3 points by 0xjnml 4y ago|2 comments
58.
by 0xjnml 4y ago
How can a precise garbage collector work when it does not know if a value is or is not a pointer?
59.
by 0xjnml 4y ago
> I think if Golang would have been invented a couple of years later it def would have had sum types. How to combine sum types and a precise garbage collector?
60.
by 0xjnml 4y ago
> it seems bogus that maps don't; this doesn't compile in Go if m is a map: It does not seem bogus to me. Values in a map are not addressable for a good reasons. It allows more freedom in implementing a map. Arrays, on the othe

More ›