![function getItemsWithNext() {
return items
.filter(item => {
if (isDeleted(item)) {
return false
}
return true
})
.map((item, i) => {
const next = items[i + 1]
return {
item,
next,
}
})
}](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:p2cp5gopk7mgjegy6wadk3ep/bafkreifjayqiaf2nznful46gpc5kf2y5gjkktlmophvgefr2nvp7uorxtm "function getItemsWithNext() {
return items
.filter(item => {
if (isDeleted(item)) {
return false
}
return true
})
.map((item, i) => {
const next = items[i + 1]
return {
item,
next,
}
})
}")
Samuel
@samuel.fm
ish - the arrays are now different lengths, so `items[i + 1]` is not necessarily the next item
3 7
Biscuitmy brain hurts but wouldn't i + 1 eventually be an out of bounds rascal or is this some javascript wizardry
2 5
ππΊππah of course. dang so close to nailing the bluesky interview challenge
1 3
James MunnsAlso, does items[i + 1] index off the end of the array? does js have an equivalent to rust's "windows", where you get an iterator over like like (0, 1), (1, 2), ... (N-2, N-1), (N-1, N)?
Also is this just iterator invalidation issues?
1 1