mething other than a
>> slice.
>>
>> You need understanding of the types and cost of operations in any
>> language, and the naming (or something else) should make the types easily
>> recognizable (and understandable).
>>
>>
>> -----Original Message---
other than a
>> slice.
>>
>> You need understanding of the types and cost of operations in any language,
>> and the naming (or something else) should make the types easily recognizable
>> (and understandable).
>>
>>
>> -----Original Message-
;> slice.
>>
>> You need understanding of the types and cost of operations in any
>> language, and the naming (or something else) should make the types easily
>> recognizable (and understandable).
>>
>>
>> -----Original Message-----
>> From: Tyl
or something else) should make the types easily
> recognizable (and understandable).
>
>
> -Original Message-
> From: Tyler Compton
> Sent: Nov 5, 2019 3:57 PM
> To: toddsu...@icloud.com
> Cc: golang-nuts
> Subject: Re: [go-nuts] Why doesn't Go include a contai
tions in any language, and the naming (or something else) should make the types easily recognizable (and understandable).-Original Message-
From: Tyler Compton
Sent: Nov 5, 2019 3:57 PM
To: toddsu...@icloud.com
Cc: golang-nuts
Subject: Re: [go-nuts] Why doesn't Go include a contains
Ian's answer addresses your question about the absence of a slice.Contains
method, but there have been discussions in the past about adding such a
feature to the language itself as well. You brought up the idea of a
builtin "contains" function, and I've seen others suggest adding something
like Pyt
On Tue, Nov 5, 2019 at 12:30 PM toddsurfs via golang-nuts
wrote:
>
> Sorry if this question reveals my newness to Go. I tried searching the
> mailing list but I couldn't find anything in a quick search. It seems like
> many languages include the ability to check if an array, or slice contain a
