introspection

It seems like graphql parser doesn't like graphql comments in the schemas? This is using the federated proxy example.

build base schema: parse graphql document string: external: unexpected token - got: COMMENT want one of: [], locations:

remote schema

input UserInput {
    userID: Int
	# Some comment
	place: String
}

In this simple Go example, it's clear that Go's stack switch causes stacktraces to wander off the right hand side of the screen. I think this is easy to fix: when trace_writer.ml, sees the symbol runtime.newstack, it should mark all currently-open stack frames as closed.

I'm not sure if there is any more custom control flow in Go code. e.g. d