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
It would be great if the library included a configuration parameter that would let users define how null values should be handled. There ought to be three options:
Any null values should trigger a failed assertion (current behavior)
Expect all null elements to be placed before -∞ (depending on sort order)
Expect all null elements to be placed after +∞ (depending on sort order)
After testing some more, it looks like #2 is the current behavior (which is the probably the best default). Still, it would be nice to have the configuration option.
It would be great if the library included a configuration parameter that would let users define how
null
values should be handled. There ought to be three options:null
values should trigger a failed assertion (current behavior)null
elements to be placed before -∞ (depending on sort order)null
elements to be placed after +∞ (depending on sort order)Maybe something like this?
The text was updated successfully, but these errors were encountered: