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
Probably still lingering 0-index use, where for select(1, 0), it really should actually be the root node, so a return of 0 is valid and in the case of select(0, 0), it should be the first closing parenthesis encountered, or the first tip in the tree. However, right now it returns either 0 or -1 (depending on implementation tested, which is wrong and thus requiring the use of select(0, 1) to refer to k=1. Basically, the semantics of select(0) and select(1) differ in that the former is k >= 1 and latter is k >= 0
The text was updated successfully, but these errors were encountered:
Probably still lingering 0-index use, where for
select(1, 0)
, it really should actually be the root node, so a return of0
is valid and in the case ofselect(0, 0)
, it should be the first closing parenthesis encountered, or the first tip in the tree. However, right now it returns either0
or-1
(depending on implementation tested, which is wrong and thus requiring the use ofselect(0, 1)
to refer tok=1
. Basically, the semantics ofselect(0)
andselect(1)
differ in that the former isk >= 1
and latter isk >= 0
The text was updated successfully, but these errors were encountered: