Change sort optional parameters from Handle to any and update SortFunc1D/2D typedef

[JoinedSenses]

• Change optional parameters from Handle to any; Not seeing any particular reason why they need to exclusively be a Handle.
• Modify the SortFunc2D typedef.
  • Remove char typedef (char cannot be coerced to any).
  • Change typeset to typedef and make the parameters any instead of int
• Change Sort(Custom/Func)1D params from int to any

[Headline]

Other than that one doc comment, this seems fine to me!

Go ahead and switch that out and I'll pull this in

[peace-maker]

any and floats aren't friends, since the float operators aren't used if a float is tagged as any. This could cause confusion when sorting float arrays.

Can you add a warning for float arrays?

[JoinedSenses]

any and floats aren't friends, since the float operators aren't used if a float is tagged as any. This could cause confusion when sorting float arrays.

Can you add a warning for float arrays?

This seems like a general sp nuisance not specific to sort stuff that folks should be aware of in general, so I feel like this isn't the best place to put that info, though I don't mind adding a note I suppose.

[Headline]

any and floats aren't friends, since the float operators aren't used if a float is tagged as any. This could cause confusion when sorting float arrays.

Can you add a warning for float arrays?

If they're retagged in the function prototype for comparison the correct operator will be used, no?

iirc you can pass in a float[] as any[], and in the comparison accept float type and not any

[JoinedSenses]

any and floats aren't friends, since the float operators aren't used if a float is tagged as any. This could cause confusion when sorting float arrays.
Can you add a warning for float arrays?

If they're retagged in the function prototype for comparison the correct operator will be used, no?

iirc you can pass in a float[] as any[], and in the comparison accept float type and not any

yep, that is also true

[asherkin]

LGTM

The SortCustom2D / SortFunc2D change is interesting because I'm pretty sure this used to work correctly (as long as the callback matched) before passing char[] to any[] was prevented. With that change and now this actually removing the unusable prototype I think we've lost the ability to sort arrays of strings.

[FortyTwoFortyTwo]

My pull request at #1124 is very identical to this apart from mine having optional data param in callbacks.
No idea why my PR gets ignored, but this PR could be updated to have SortFunc(1D/2D/ADTArray) without having data param as optional.

[KyleSanderson]

@asherkin are you still OK with this?