Roman Sharkov

@merhalak In Go - types are read and written from left to right in a (western) human-friendly way. ```go // some absurdly complex type: **[]map[int]*T ``` This is a **pointer**...

@beoran There is no problem. ## Why immutable scalar types are inevitable - Part 1 Scalar types are not immutable **because they can still be reassigned**. Immutable scalar types cannot...

@beoran **Think of types as interfaces to memory**. A `mut int` is an interface to 4/8 bytes in memory with methods like `Read`, `Set`, `Increment` and `Decrement`. An `immut int`...

@deanveloper that's right, it was meant to be an array actually. Fixed it, need to go get some sleep ASAP. Let's discuss the question whether or not immutability is necessary...

@beoran What's the third keyword you're referring to? I've only proposed `mut` and `immut` here. Immutable types are not just about "_accidental modification to function arguments_", they're about accidental modification...

I'd like to begin my answer with a quote of [Russ Cox](https://github.com/rsc), one of the core Google Go team members, from his speech at the [GopherConSG](https://2018.gophercon.sg) in May 2018: https://youtu.be/F8nrpe0XWRg?t=3m12s...

@200sc > You should resolve the verbosity problem for this proposal to add any clarity. Right now spreading `const` everywhere hurts readability in a way that similarly hurts clarity, and...

@beoran > I think that because this kind of problem is rare, the costs outweigh the benefits. This is a controversial statement. I personally disagree with it because experience has...

> @romshark can you please verify? I've [upgraded the reproduction example](https://github.com/romshark/gqlgen-2207-reproduction/commit/2eaa5bfede768b4f63d4c109e9939fa43c1a30b6) to master (53ca207) but `go generate` still won't fail so this issue remains open. The [PR for vektah/gqlparser](https://github.com/vektah/gqlparser/pull/227) looks...

https://github.com/romshark/gqlgen-2195-reproduction @frederikhors you're welcome