ordered_set
A simple implementation for an Ordered Set for Dart.
It accepts either a comparator function that compares items for their priority or a mapper function that maps items to their priority.
Unlike Dart's SplayTreeSet or SplayTreeMap classes, it allows for several different elements with the same "priority" to be added.
It also implements Iterable, allowing you to iterate the contents (in order) in O(n) (no additional overhead).
Usage
A simple usage example:
import 'package:ordered_set/ordered_set.dart';
main() {
final items = OrderedSet.simple<num, int>();
items.add(2);
items.add(1);
print(items.toList()); // [1, 2]
}
But it can accept multiple items with the same priority:
import 'package:ordered_set/ordered_set.dart';
main() {
final items = OrderedSet.mapping<String, Person>((p) => p.name);
items.add(Person('Alice', 'Engineering'));
items.add(Person('Bob', 'Accounting'));
items.add(Person('Alice', 'Marketing'));
print(items.toList()); // [Alice, Alice, Bob]
}
Comparing
In order to assist the creation of Comparators, the Comparing class can be used:
// sort by name length
final people = OrderedSet.comparing<Person>(Comparing.on((p) => p.name.length));
// sort by name desc
final people = OrderedSet.comparing<Person>(Comparing.reverse(Comparing.on((p) => p.name)));
// sort by role and then by name
final people = OrderedSet.comparing<Person>(Comparing.join([(p) => p.role, (p) => p.name]));
Note that you could instead just create a MappingOrderedSet instead:
final people = OrderedSet.mapping<num, Person>((p) => p.name.length);
// ...
Mapping vs Comparing
There are two main implementations of the OrderedSet interface:
ComparingOrderedSet: the simplest implementation, takes in aComparatorand does not cache priorities. It uses Dart'sSplayTreeSetas a backing implementation.MappingOrderedSet: a slightly more advanced implementation that takes in a mapper function (maps elements to their priorities) and caches them. It uses Dart'sSplayTreeMapas a backing implementation.
In order to create an OrderedSet, however, you can just use the static methods on the interface
itself:
OrderedSet.comparing<E>([comparator]): creates aComparingOrderedSetwith the givenComparator.OrderedSet.mapping<K, E>([mapper]): creates aMappingOrderedSetwith the given mapper function.OrderedSet.comparable<K, E>(): ifE extends Comparable<K>, this is a simpler way of creating aMappingOrderedSetwith identity mapping.OrderedSet.simple<E>(): ifE extends Comparable<E>, this is an even simpler way of creating aMappingOrderedSetwith identity mapping.
Querying
You can register a set of queries, i.e., predefined sub-types, whose results, i.e., subsets of
this set, are then cached. Since the queries have to be type checks, and types are runtime
constants, this can be vastly optimized.
You can then filter by type by using the query method (or using whereType; which is overridden).
Note that you can change strictMode to allow for querying for unregistered types; if you do so,
the registration cost is payed on the first query.
Contributing
All contributions are very welcome! Please feel free to create Issues, help us with PR's or comment your suggestions, feature requests, bugs, et cetera. Give us a star if you liked it!