Ahhrg, sorry, sorry, sorry!
My reply to this message should have gone to the last one of user T L
not yours.

I'd like to blame the Web UI, but it was just me being lazy. Sorry.

V.

Am Freitag, 26. August 2016 21:13:16 UTC+2 schrieb xiio...@gmail.com:
>
> *"I feel the effort is made to forbid converting []Age into []int instead 
> now."*
>
> I don't agree that allowing this conversion would be 'easier' than not 
> allowing.
>
> Allowing it requires the additional step of splitting/extracting from the 
> slice the element type and checking that (for assignability)
>
> I am fairly certain that currently that step isn't performed and the slice 
> is treated as a type unto itself, not as some sort of "composite type"
>
> It is/would be an extra step to achieve what is suggested in the original 
> example.
>
> I feel you are asking for extra recursion in the type analysis the 
> compiler does.
>
> I haven't checked the compiler code for this but would bet that currently 
> there is no step disallowing such an assignment.
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to