You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the first part tells you about what happens if you use it with a simple sorted list as the left argument, with no indication at the front that it can be used with other left arguments. There is a definition and a mathematical clarification as to what the keyword does. There are no examples given. Only at the end of the first part is it mentioned that the keyword also works with tuples (that's the old word for a dictionary?) and table columns (which I think is misleading wording: a column is just a list, we're trying to say that it works on tables).
the second part tells you about what happens if you use it with a three-column table as the left argument. I don't think there's any reason it should be three, as far as I know, the keyword is more general than that. I think the wording is a bit on the technical side, but a good example can help massively. The example given though is wrong, as these are examples for the first part (list as the left argument). Also, interestingly, for "not found", the result here is 0N instead of -1, this is not documented.
the third part tells you about what happens if you use it with a three-column table as the left argument while the last column is sorted. Here, it makes more sense that it's three, as you need at least three columns to explain how the search works, but still, it doesn't only work with three. The example given is okay, as the result exactly the same as if the third column wasn't sorted, and only the performance aspect is relevant.
The text was updated successfully, but these errors were encountered:
Submitted by rpinter for https://code.kx.com/q/ref/bin/
The text was updated successfully, but these errors were encountered: