On Mon, Nov 27, 2017 at 3:18 PM Stefan Nilsson <trolleriprofess...@gmail.com>
wrote:
> I fully understand that this can be implemented in many different ways.
That's not my question. Splitting words about "consists of" and "has a"
doesn't add much to the discussion.
I think the distinction is essential. Consider/compare to:
i := 42
Per specs, the variable consists of 32 or 64 bits representing the number
42 and it also has a type. Static in this case, but that's not important.
The point is that for a value to have an observable type, the value per se
does not need to _include_ the type information. Including it in the value
of an interface variable is fine and everything, but in no way a necessity.
Meaning: implementation detail interesting mostly for the compiler/runtime
people only. Why talk about a type descriptor _value_ when there can be
none?
--
-j
--
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.
