Go runtime: 4 years later
1–10 of 296 posts
Re: Go runtime: 4 years later
#2Re: Go runtime: 4 years later
#3Re: Go runtime: 4 years later
#4Still yearning for an Ocaml-like language that uses the Go runtime.
Re: Go runtime: 4 years later
#5Still yearning for an Ocaml-like language that uses the Go runtime.
But I'm ignorant: is the Go runtime built in any way to accomodate third party languages? Apart from writing an interepreter in Go, is there a good way to target it?
Re: Go runtime: 4 years later
#6Still yearning for an Ocaml-like language that uses the Go runtime.
I don't like Go, but I think I would use that. But I'm ignorant: is the Go runtime built in any way to accomodate third party languages? Apart from writing an interepreter in Go, is there a good way to target it?
Edit: https://github.com/minio/c2goasm seems to slightly go in that direction.
Re: Go runtime: 4 years later
#7Still yearning for an Ocaml-like language that uses the Go runtime.
I don't like Go, but I think I would use that. But I'm ignorant: is the Go runtime built in any way to accomodate third party languages? Apart from writing an interepreter in Go, is there a good way to target it?
Something else is that the semantics of the Go language itself are purposely limited in ways that help build an efficient runtime easily. So even if you could target the Go runtime easily, it would impose limits to what the language can do as I understand.
Re: Go runtime: 4 years later
#8Still yearning for an Ocaml-like language that uses the Go runtime.
Re: Go runtime: 4 years later
#9Still yearning for an Ocaml-like language that uses the Go runtime.