[go-nuts] Why regexp.FindIndex doesn't return a [2]int but a []int?

On Thursday, September 4, 2014 6:58:40 AM UTC-7, opennota wrote:

Arrays can't be nil, that's why, I guess.

On Thu, Sep 4, 2014 at 7:28 AM, David DENG wrote:
If so, an array of [-1, -1] can express the result of not found in
FindIndex, and zero length of slice can serve for FindAllIndex

David
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

If so, an array of [-1, -1] can express the result of not found in
FindIndex, and zero length of slice can serve for FindAllIndex

David

On Thu, Sep 4, 2014 at 12:41 PM, Dobrosław Żybort wrote:
You can always file an issue (to consider for Go2):
https://code.google.com/p/go/issues/list?q=label:Go2

W dniu czwartek, 4 września 2014 16:28:39 UTC+2 użytkownik David DENG
napisał:
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

FindIndex,

The downside, of course, is that something like []int{-1, -1} is a
much less common, less obvious, and uglier-to-code-around sentinel
than nil.

On 04/09/14 23:29, David DENG wrote:
I don't think so. strings.Index (and friends) also returns -1 for not
found. This is a very common used mark for searching functions.
FindIndex,

The downside, of course, is that something like []int{-1, -1} is a
much less common, less obvious, and uglier-to-code-around sentinel
than nil.

--
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+unsubscribe@googlegroups.com
For more options, visit https://groups.google.com/d/optout.

On Fri, Sep 5, 2014 at 2:15 AM, Nick Craig-Wood wrote:
IMHO it should be returning a

type FindResult struct {
Start int
End int
}

Which would be just as memory efficient as a [2]int

Then you could define a NotFound method on it

func (fr FindResult) NotFound() bool {
return fr.Start < 0
}

--
Nick Craig-Wood <nick@craig-wood.com> -- http://www.craig-wood.com/nick

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.