Ok thx
On Monday, July 8, 2019 at 6:29:34 AM UTC+2, Liam wrote:
>
> Get, you may get more response on this by posting to golang-dev...
>
> On Sunday, July 7, 2019 at 3:06:55 PM UTC-7, Gert wrote:
>>
>> My intelligence is that of a ping pong ball but think it's time to clean
>> up de go compiler b
On Saturday, July 6, 2019 at 8:51:19 AM UTC+2, go je wrote:
>
> Is the Category "Games" gaining attention in the go community?
> Are the Developers writing for production level?
> Do we have an examples?
>
There is no game engine in the standard library but you will find Go game
engines on githu
Get, you may get more response on this by posting to golang-dev...
On Sunday, July 7, 2019 at 3:06:55 PM UTC-7, Gert wrote:
>
> My intelligence is that of a ping pong ball but think it's time to clean
> up de go compiler backlog so ping pong balls like me have a chance to
> understand the compil
I have no doubt there is huge amount of people who love the exceptions, and
I agree with you
that is precisely this crowd that pushed this agenda forward.
But I found following true, anything that can fail will fail. E.g. any type
of IO operation.
It's not a question of if but when.
What that
My intelligence is that of a ping pong ball but think it's time to clean up
de go compiler backlog so ping pong balls like me have a chance to
understand the compiler code.
For example from the compiler readme
```
Note that the `go/*` family of packages, such as `go/parser` and `go/types`,
have
On Thursday, 4 July 2019 22:45:40 UTC+2, mh cbon wrote:
>
>
> less stupid the oprator could infer various things based on static rules,
> very much like value/ptr initialization implies a few static rules.
>
> on os.IsNotExist(err):
> on err == io.EOF:
> on err.(*os.PathError):
>
>
Th
