Thanks to Ian's pointers I was able to get to a state where "go build"
command passes successfully. For the moment my compile/link/asm stubs
produce minimally viable outputs (which are mostly empty), but the go tool
is happy enough with the contents. Next step of plugging GopherJS logic in
should n
> I suspect this will give you trouble over time.
That's the question I've been pondering a lot lately. I know for sure that
trying to keep up with the go tool evolution *is* a lot of trouble. I'm
trying to experiment with alternatives to get some sense for how they
actually compare. Using go/bu
On Mon, Jan 11, 2021 at 11:03 AM Alexander Zhirov wrote:
>
> At the moment there are at least three alternative implementations of Go that
> I know of (and there are probably some I don't): gccgo, tinygo and gopherjs.
> Of the three, only gccgo is supported by the go tool out of box. Looking at
Hi all,
At the moment there are at least three alternative implementations of Go
that I know of (and there are probably some I don't): gccgo, tinygo and
gopherjs. Of the three, only gccgo is supported by the go tool out of box.
Looking at the source code, gc ang gccgo have their own implementat
