We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comparable
Sort
Currently, we only have comparators for number types. We should implement coherent logic around handling comparable types in general.
List.Comparable
F
T
(F: Kind, T: Comparable[]) --> Boolean
String.Compare
(A: String, B: String) --> -1 | 0 | 1
Object.Compare
(F: Kind, A: Record, B: Record) --> -1 | 0 | 1
List.Sort
compare
(T: Comparable[]) --> ?[]
List.SortOn
(F: Kind, T: ?[]) --> ?[]
List.Max
List.Min
The implementation should include unit tests and JSDoc comments that adhere to the guidelines established in the style-guide/ directory.
style-guide/
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently, we only have comparators for number types. We should implement coherent logic around handling comparable types in general.
List.Comparable
F
and a listT
, return true iff every element ofT
is comparable usingF
.(F: Kind, T: Comparable[]) --> Boolean
String.Compare
(A: String, B: String) --> -1 | 0 | 1
Object.Compare
(F: Kind, A: Record, B: Record) --> -1 | 0 | 1
List.Sort
T
of comparable types, sort the elements using the built-incompare
methods and return the result.(T: Comparable[]) --> ?[]
List.SortOn
F
and a listT
of comparable types, sort the elements using the user-supplied comparator and return the result.(F: Kind, T: ?[]) --> ?[]
List.Max
F
and a listT
of comparable types, return the maximum.List.Min
F
and a listT
of comparable types, return the minimum.The implementation should include unit tests and JSDoc comments that adhere to the guidelines established in the
style-guide/
directory.The text was updated successfully, but these errors were encountered: