Dmitri Shuralyov

In case it's helpful as a reference, [here](https://godoc.org/github.com/shurcooL/play/231)'s a proof of concept git server over SSH protocol. It uses `git-upload-pack` and `git-receive-pack` binaries (just `git-upload-pack` is sufficient for read access).

@stephanwesten It has to do with [build constraints](https://golang.org/cmd/go/#hdr-Build_constraints) and the fact that `GOARCH` is `arm64` instead of `amd64` on M1. `typeInfoForType` is defined in a file named `typeinfo_amd64.go`, which is...

> This seems to have the potential to break expected behavior, if stdout isn't flushed before exit. @flimzy, `os.Exit` exits the process immediately as well, it doesn't wait for buffers...

Thanks for this @Lekensteyn. At a high level, this makes sense.

I think it does. Are you referring to how writing to `os.Stdout` in GopherJS includes some internal buffering for browsers, so that a single line of output maps to a...

We should take this documented behavior into account: > In the browser, calling `os.Exit` (e.g. indirectly by `log.Fatal`) also does not terminate the execution of the program. For convenience, it...

Thanks for the ping, and sorry about the delay. I will try to find some time to work on this. I still need to get a better understanding of the...

Both `runtime.FuncForPC` and `runtime.Callers` are not supported in GopherJS. They have stub implementations: ```Go func FuncForPC(pc uintptr) *Func { return nil } func Callers(skip int, pc []uintptr) int { return...

I can confirm this appears to be resolved on my WIP implementation of #388. ``` $ go build import cycle not allowed package github.com/shurcooL/play/31 imports github.com/shurcooL/play/31/a imports github.com/shurcooL/play/31/b imports github.com/shurcooL/play/31/a...

Which fix are you referring to? The one I mentioned in the comment above was https://github.com/gopherjs/gopherjs/pull/485#issuecomment-281441761, which is an abandoned PR. **Edit:** To be clear, this is an open and...