bugs: list returns wrong results (likely bug in drop function) about list HOT 12 CLOSED

See #65. I've found the bug and reproduced it with a smaller test case. I'd love to get your feedback on the alternative solution I mention in the PR 😄

Thanks again for reporting the issue with a nice and simple test case 👍

from list.

Just lobbying for a bugfix release when possible :-)

I've just released a new version 👍

from list.

simplified the first bug to just two drops:

const L = require("list")

let f = L.list()
for (let i=0;i<1329;i++) {
    f = L.append(i, f);
}

const xx = L.drop(3, L.drop(201, f))
console.log(L.first(xx))
console.log(L.nth(0, xx))

-- sanity check
const xx1 = L.fromArray(L.toArray(xx));
console.log(L.first(xx1))
console.log(L.nth(0, xx1))

output is =>

201
204
204
204

from list.

Thank you for reporting the issue @emmanueltouzery. I'm looking into it!

from list.

did you check that your fix fixes both issues reproduced through the first script? The second issue from the first script may be independent because drop and dropLast use only slice. In that second issue I don't see first and last playing any role?

from list.

No, I missed that there were two parts and I only tested with the second code. I'll take a look at the other problem as well 😄

from list.

yes unfortunately there are two bugs, I ran the test script from your PR branch:

FIRST ISSUE first() doesn't agree with nth(0)
204
204
SECOND ISSUE list of 4 drop first and last, wrong result
[ 201, 202, 203, 204 ]
[ 201, 202 ]

This kind of bugs seem like showstoppers to me :-(

from list.

You didn't forget about other bug did you? Closing the bug makes it unclear

from list.

You didn't forget about other bug did you? Closing the bug makes it unclear

Don't worry, I didn't 😄

I actually didn't close the issue myself. GitHub automatically closed the issue because I merged the PR #65. Since the PR contained the text "Fixes #64" GitHub thought the issue was fixed.

This kind of bugs seem like showstoppers to me :-(

I agree. List shouldn't have any bugs. See #66. That should fix the issue.

from list.

Yes in general in the commits i say "ref #bug" if it's related to the bug without fixing it. Great otherwise! Hope you make a bugfix release soon :-)

from list.

Yes in general in the commits i say "ref #bug" if it's related to the bug without fixing it.

That's a great tip!

Both issues should be fixed now so I'll close 😄

from list.

Sure let's close. Just lobbying for a bugfix release when possible :-)

from list.