> go has its own bio, used by its self-contained source tree. > why can't it just use the one it expects? > i think you explained it once, but i've reverted to being mystified.
Does Go, the tool chain itself, need libbio? If not, then it is there only for building Go on platforms other than Plan 9 and the Go libbio should be a subset of the Plan 9 one. Breaking this concept seems unnecessary, not unforgivable: Go does this with libmach, but there the details are much more complex and a merge of libmachs between Go and Plan 9 would in any case be an asset. As an interesting issue, we could have avoided introducing 21-bit runes in Plan 9 by extracting a libutf from libc for use in Plan 9, but we would have gained some time and nothing else. The same, more or less, applies to libbio, in my opinion. ++L
