Re: [go-nuts] Calling the Go compiler inside of tests

2017-12-15 Thread Glen Newton
YES! This looks like it is exactly what I needed! Thanks! Glen On Friday, December 15, 2017 at 3:55:51 PM UTC-5, Ian Cottrell wrote: > > You could just use the go/types package to typecheck the result instead of > compiling it, depending on exactly what you want to check that may be > enough. >

Re: [go-nuts] Calling the Go compiler inside of tests

2017-12-15 Thread 'Ian Cottrell' via golang-nuts
You could just use the go/types package to typecheck the result instead of compiling it, depending on exactly what you want to check that may be enough. On Fri, Dec 15, 2017 at 8:37 AM Tamás Gulácsi wrote: > When you invoke "go test", it compiles a test binary and calls that. > Why can't you ju

[go-nuts] Calling the Go compiler inside of tests

2017-12-15 Thread Tamás Gulácsi
When you invoke "go test", it compiles a test binary and calls that. Why can't you just repeat that? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+u

[go-nuts] Calling the Go compiler inside of tests

2017-12-15 Thread Glen Newton
Hello, Apologies if this has already been discussed. I have a go tool (chidley - https://github.com/gnewton/chidley) that converts xml to Go struct code by examining a sample file (perhaps very large) of the XML (It can also generate Java JAXB code...). Production examples of generated structs: