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
This is a new datatype introduced in 5.2 for value ranges. See here.
5.2
Looks like we could represent it as:
struct DateRange<F> { gte: Date<DefaultDateMapping<F>>, lte: Date<DateRangeMapping<F>>, }
Some things to think about:
gt
lt
gte
lte
Ranges also support number types so they'll need to be added.
The text was updated successfully, but these errors were encountered:
I think it's worth copying Rust's ranges, so the lower bound is gte and the upper bound is lt.
Sorry, something went wrong.
For completeness these bounds could also be represented as enums:
enum LowerBound<T> { LessThan(T), LessThanOrEqual(T), } enum UpperBound<T> { GreaterThan(T), GreaterThanOrEqual(T), }
So you could choose whatever bounds you want, but won't have the invalid case of specifying both lt and lte.
No branches or pull requests
This is a new datatype introduced in
5.2
for value ranges. See here.Looks like we could represent it as:
Some things to think about:
gt
orlt
. Anything that can be represented bygt
orlt
can be done bygte
andlte
so not a big priority.Ranges also support number types so they'll need to be added.
The text was updated successfully, but these errors were encountered: