Yes, it should.
Alan
--
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.
To view this discussion on the web visit
In this:
func Map(type S, Element)(s S, f func(Element) Element) S {
Why is Slice not mentioned anywhere?
Shouldn't it be:
func Map(type S, Element Slice) [..]
On Tuesday, 30 July 2019 09:04:26 UTC+9, Ian Lance Taylor wrote:
>
> On Mon, Jul 29, 2019 at 2:35 PM Mandolyte >
> wrote:
> >
On Mon, Jul 29, 2019 at 2:35 PM Mandolyte wrote:
>
> In this code snippet:
>>
>> func Map(type S, Element)(s S, f func(Element) Element) S {
>> r := make(S, len(s))
>> for i, v := range s {
>> r[i] = f(s)
>> }
>> return r
>> }
>
> Shouldn't the line in the loop be: r[i] = f(v)
Yes. Thanks.
Ian
In this code snippet:
> func Map(type S, Element)(s S, f func(Element) Element) S {
> r := make(S, len(s))
> for i, v := range s {
> r[i] = f(s)
> }
> return r}
>
> Shouldn't the line in the loop be: r[i] = f(v)
On Monday, July 29, 2019 at 2:17:22 PM UTC-4,
On Sun, Jul 28, 2019 at 1:15 PM Jon Bodner wrote:
>
> I did a first read through the proposal and it looks very good. I had one
> question: when giving the example of how to implement Sorting using
> orderedSlice, the type parameter is declared to be comparable. Should that be
>
I missed this. Do you have a link to the proposal?
--
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.
To view this
Hello,
I did a first read through the proposal and it looks very good. I had one
question: when giving the example of how to implement Sorting using
orderedSlice, the type parameter is declared to be comparable. Should that be
contracts.Ordered?
Thanks,
Jon
--
You received this message
