* jlforr...@berkeley.edu [190329 15:28]:
> Thanks everyone for responding!
>
> However, in the case that I illustrated there is no such problem. I
> would have thought that the language would allow this construct with
> any expression on the right side, as long as it only has one map
> access.
>
On Fri, Mar 29, 2019 at 8:27 PM wrote:
> However, in the case that I illustrated there is no such problem. I would
have thought that the
> language would allow this construct with any expression on the right
side, as long as it only has one
> map access.
Consider
type v struct{
* jlforr...@berkeley.edu [190329 11:16]:
> I get the error
>
> assignment mismatch: 2 variable but 1 values
>
> for the assignment statement in Part 2 but the assignment statement in
> Part 1 compiles. Both assignment statements have the same number of
> values, but it appears that referencing
On Fri, Mar 29, 2019 at 4:16 PM wrote:
> I wonder if what I'm seeing is expected.
It is. The language specification defines the selector to produce a single
value.
--
-j
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from
