turbo-editors/turbo-core · 2026-09-12-non-go-dependencies.md

⑂ main

2026-09-12-non-go-dependencies.md · 19 lines · 1.6 KBmarkdown    Blame HistoryRaw
   1# 2026-09-12 — Non-Go dependencies: none
3A single question, answered; no code touched, nothing in flight.
5**Question**: does turbo-core depend on any non-Go library?
7**Finding**: no, and here is the evidence so the next session need not re-run it.
9- `go.mod`: three direct (`tcell/v2`, `BurntSushi/toml`, `golang.org/x/sys`), five indirect (`gdamore/encoding`, `go-colorful`, `uniseg`, `x/term`, `x/text`). All pure Go.
10- `grep -rn '"C"' --include='*.go' .` → nothing. No cgo in this repository.
11- `CGO_ENABLED=0 go build ./...` → OK. That is the decisive check: it proves nothing in the graph *requires* cgo.
12- Scanning each module in `GOMODCACHE` for `*.c`/`*.h`: only `x/sys` has any — `cpu/cpu_gccgo_x86.c` and `unix/gccgo_c.c`. Both are for the **gccgo** compiler and are not built by the standard `gc` toolchain. Do not report these as a native dependency.
13- `net` shows up in `go list -deps` only through `lsp/fakeserver_test.go` and `app/fakelsp_test.go`. Test-only.
15**The distinction worth keeping**: no *link-time* native dependency, but the running editor does exec external *binaries* — `/bin/sh` (`tools/run.go:19`, `app/toolchain.go:35`) for terminal windows and the tools menu, and the profile's LSP server command (`lsp/server.go:92`, `profile.Profile.Command`). If the question ever comes back phrased as "what does a user need installed", that is the answer; "what does it link against" is nothing.
17**Consequence**: a statically linked, cross-compilable binary with no C toolchain needed.
19**Next steps**: none opened by this session. `summary.md`'s "Two direct dependencies plus one" decision (line ~94) still holds and was left byte-for-byte alone.

🛟 Updated. 28d5985 k33g 11h ago	1	# 2026-09-12 — Non-Go dependencies: none
	2
	3	A single question, answered; no code touched, nothing in flight.
	4
	5	Question: does turbo-core depend on any non-Go library?
	6
	7	Finding: no, and here is the evidence so the next session need not re-run it.
	8
	9	- `go.mod`: three direct (`tcell/v2`, `BurntSushi/toml`, `golang.org/x/sys`), five indirect (`gdamore/encoding`, `go-colorful`, `uniseg`, `x/term`, `x/text`). All pure Go.
	10	- `grep -rn '"C"' --include='*.go' .` → nothing. No cgo in this repository.
	11	- `CGO_ENABLED=0 go build ./...` → OK. That is the decisive check: it proves nothing in the graph requires cgo.
	12	- Scanning each module in `GOMODCACHE` for `.c`/`.h`: only `x/sys` has any — `cpu/cpu_gccgo_x86.c` and `unix/gccgo_c.c`. Both are for the gccgo compiler and are not built by the standard `gc` toolchain. Do not report these as a native dependency.
	13	- `net` shows up in `go list -deps` only through `lsp/fakeserver_test.go` and `app/fakelsp_test.go`. Test-only.
	14
	15	The distinction worth keeping: no link-time native dependency, but the running editor does exec external binaries — `/bin/sh` (`tools/run.go:19`, `app/toolchain.go:35`) for terminal windows and the tools menu, and the profile's LSP server command (`lsp/server.go:92`, `profile.Profile.Command`). If the question ever comes back phrased as "what does a user need installed", that is the answer; "what does it link against" is nothing.
	16
	17	Consequence: a statically linked, cross-compilable binary with no C toolchain needed.
	18
	19	Next steps: none opened by this session. `summary.md`'s "Two direct dependencies plus one" decision (line ~94) still holds and was left byte-for-byte alone.