3 ms·
No, a [closed, open) interval of [Jan 13, Jan 13) would give you 0 nights. A [closed, open) interval of calendar dates incidentally does correspond to the numb
by sshine 4y ago
No, a [closed, open) interval of [Jan 13, Jan 13) would give you 0 nights.
A [closed, open) interval of calendar dates incidentally does correspond to the number of nights spent. So booking [Jan 13, Jan 14) would mean spending one night. The hotel gives you until, say, 11:00 to get out the next day without paying for that date.
Half-open intervals are neat because they concatenate without overlap.
So [Jan 13, Jan 14) + [Jan 14, Jan 15) = [Jan 13, Jan 15).
This is a very convenient property when dealing with dates in particular, but also indices over arrays.
- Rygian 4y agoSo it boils down to what is being represented: an amount of items versus an amount of _boundaries_ across items. When I'm booking that stay between Jan 13th and Jan 14th, and I am presented with options, the ones that say "sleeps 2" does not mean [1, 2) but rather [1, 2] and the one that says "sleeps 6" does not mean [1, 6) but rather [1, 6].
- jissa 4y agoBut I don't think these are equivalent. When looking for a booking you are using an interval. When looking at room capacity you are looking for a minimum. This is not the same as an interval. If you are looking for "sleeps 6" that is your bare minimum acceptance in capacity. You are not interested for the [1, 6] interval. Nothing below 6 makes sense. Even if you wanted to force the interval use here, I'd say you'd be looking for the [6, INF) interval. That is, rooms with capacity of at least 6 (but having more capacity is fine).