Looks the multiple trick is not a theory. That is cool!
I don't know if this is an issue known for a long time.
If it is not, I would file an issue some time later.
On Mon, Dec 23, 2019 at 1:04 PM Axel Wagner
wrote:
> Sorry for the off-list response, that was unintentional.
>
> I think it might
Sorry for the off-list response, that was unintentional.
I think it might be okay, but I could also think of a couple of reasons
against it. AFAIK, Go programs for the playground are compiled with a
patched stdlib (at least they used to be, to do the faketime-stuff. I don't
know if we're already a
;(, looks the last comment doesn't appear in go-nuts.
On Mon, Dec 23, 2019 at 9:37 AM T L wrote:
>
> > However, the playground has no GOROOT or build cache or anything
> available: https://play.golang.org/p/RPGwtZSJSPQ
>
> But, isn't it ok to let the playground own a GOROOT?
>
> On Mon, Dec 23,
> However, the playground has no GOROOT or build cache or anything
available: https://play.golang.org/p/RPGwtZSJSPQ
But, isn't it ok to let the playground own a GOROOT?
On Mon, Dec 23, 2019 at 5:47 AM Axel Wagner
wrote:
> Parsing is not the problem, type-checking is. For that, the
> type-inform
The code from the std go/types package parses the demo code well on local
machine, but not in playground:
https://play.golang.org/p/BlHHgdscaXj
What is the cause?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group a
