On Friday, October 21, 2016 at 9:53:14 PM UTC+8, Henrik Johansson wrote:
>
> The confusion I have had is rather with nilability.
> A channel can be nil even though it is not explicitly a pointer.
>
Someone think pointers should be distinguished from
channel/map/slice/interface/function.
For example, like other languages, still use null for pointer zero values.
>
> The whole "call by reference" debate is fun but usually with beer...
>
> fre 21 okt. 2016 kl 15:39 skrev Ian Lance Taylor <ia...@golang.org
> <javascript:>>:
>
>> On Thu, Oct 20, 2016 at 10:47 PM, T L <tapi...@gmail.com <javascript:>>
>> wrote:
>> >
>> > On Friday, October 21, 2016 at 1:11:32 AM UTC+8, Ian Lance Taylor wrote:
>> >>
>> >> On Thu, Oct 20, 2016 at 6:47 AM, T L <tapi...@gmail.com> wrote:
>> >> >
>> >> > On Thursday, October 20, 2016 at 4:46:52 PM UTC+8, Dave Cheney wrote:
>> >> >>
>> >> >> What is a pointer wrapper value?
>> >> >
>> >> >
>> >> > struct {
>> >> > p *T
>> >> > }
>> >> >
>> >> >>
>> >> >>
>> >> >> in all seriousness, if you review the git history of the Go spec
>> you'll
>> >> >> find the word "reference" was purged about two years ago, in
>> effect, to
>> >> >> try
>> >> >> to stem these discussions.
>> >> >
>> >> >
>> >> > Yes, I found many old docs and old web pages are still using the word
>> >> > "reference value".
>> >> > I think it is an unnecessary word. The concepts of values and pointer
>> >> > values
>> >> > are sufficient to understand Golang values well.
>> >>
>> >> I have a minor objection. I don't know what a "reference value" is.
>> >> Alan spoke about "reference types", and sometimes, in the past, before
>> >> we realized that it was confusing, the Go docs also talked about
>> >> "reference types."
>> >>
>> >> I don't think we ever talked about "reference values." Perhaps a
>> >> "reference value" is a value whose type is a "reference type."
>> >> However, people (not Go people, computer programming people in
>> >> general) also talk about "passing by reference" as opposed to "passing
>> >> by value", so combining the two opposing terms "reference" and "value"
>> >> into a single phrase is confusing.
>> >
>> > This faq, "Why are maps, slices, and channels references while arrays
>> are
>> > values?", https://golang.org/doc/faq#references.
>> > thinks maps, slices, and channels are references. I think the
>> "references"
>> > here means "reference values".
>>
>> As Marvin said in his reply, it doesn't.
>>
>> I'm not trying to say that "reference value" could not have a meaning.
>> I'm saying that I've never seen that phrase before, and given the long
>> history of discussions using these words I find it confusing.
>>
>> Ian
>>
>> --
>> 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...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
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.
