News for hackers. Stuff that matters.

A comment on The ups and downs of porting 50k lines of C++ to Go (2015). Parent comment

Re:The ups and downs of porting 50k lines of C++ to Go (2015) by 314 on Thursday March 14, 2019 @06:22AM (#19387900)
In python slice[0:-1] drops the last element. To get the same effect in Go you need world := b[:len(b)-1]. The len() needs to be there (your example is a different case).
[ Parent | on HN ]
Re:The ups and downs of porting 50k lines of C++ to Go (2015) by laumars on Thursday March 14, 2019 @06:26AM (#19387926)
Yes, I was the one who made the comment about Go's lack of a -1 for slices in the first place. ;)

I was actually referencing the 0 part and thus saying Go does already have some syntactic sugar when dealing with slices. ie you can do:

   slice[5:]   // slice[:len(slice)]
but not

   slice[5:-1] // slice[:len(slice)-1]
Which is a great pity.

However I'll update my previous comment to make that clearer because I can totally understand how it reads confusingly.

[ Parent | on HN ]