[Octave-bug-tracker] [bug #61752] unique.m FAIL in test suite

[Markus Mützel]

Follow-up Comment #7, bug #61752 (project octave):

I haven't looked into it. But I'm guessing `unique` sorts its input before
finding (adjacent) duplicates. Since sorting NaN values doesn't work correctly
with visibility flags (see bug #61711), the Inf values don't appear adjacent
to each other after that step and aren't identified as non-unique...

If that's the case, something like this might not work either (can't test atm
because I don't have an affected version at hand):

unique ([1,NaN,2,NaN,2])



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61752>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/