Re: [HACKERS] 9.3: Empty arrays returned by array_remove()

2013-05-31 Thread Noah Misch
On Fri, May 31, 2013 at 08:55:49AM +0100, Dean Rasheed wrote: > On 31 May 2013 08:34, Brendan Jurd wrote: > > On 31 May 2013 02:52, Dean Rasheed wrote: > >> Testing 9.3beta, it seems that array_remove() may return an empty 1-d > >> array whose upper bound is lower than its lower bound. I know tha

Re: [HACKERS] 9.3: Empty arrays returned by array_remove()

2013-05-31 Thread Dean Rasheed
On 31 May 2013 08:34, Brendan Jurd wrote: > On 31 May 2013 02:52, Dean Rasheed wrote: >> Testing 9.3beta, it seems that array_remove() may return an empty 1-d >> array whose upper bound is lower than its lower bound. I know that we >> discussed allowing this kind of array, but I don't think that

Re: [HACKERS] 9.3: Empty arrays returned by array_remove()

2013-05-31 Thread Brendan Jurd
On 31 May 2013 02:52, Dean Rasheed wrote: > Testing 9.3beta, it seems that array_remove() may return an empty 1-d > array whose upper bound is lower than its lower bound. I know that we > discussed allowing this kind of array, but I don't think that > discussion reached any conclusion, other than

[HACKERS] 9.3: Empty arrays returned by array_remove()

2013-05-30 Thread Dean Rasheed
Testing 9.3beta, it seems that array_remove() may return an empty 1-d array whose upper bound is lower than its lower bound. I know that we discussed allowing this kind of array, but I don't think that discussion reached any conclusion, other than to agree that the current empty 0-d array behaviour