Still working, kinda.
I’m being held up by the number of bugs I’m finding (and taking the time to try to get fixed) and that the go-devel team have gone and gotten distracted (best case) with their panic()/recover() feature and aren’t reviewing many CLs just now.
There hadseemed little point in pushing on with local patches to the main Go code when I can submit a CL (and until recently) get it committed promptly. If I can’t do that, the appropriate thing to do is perhaps just to push along with the port, accepting things that don’t work, putting in extra workarounds, and duplicating even more code, crossing my fingers that it’ll be able to be cleaned up one day.
My software development experience suggests it’s better to get it right the first time as it’s almost always impossible to go back, so I’m reluctant to change tack, but maybe I need to, if Go is to run on NetBSD.