![]() Specifically, when it sees these contracts: (and/c real? negative?) (and/c real? positive?) (and/c real? (not/c positive?)) (and/c real? (not/c negative?)) it generates the corresponding use of >=/c, <=/c, </c, or >/c, but those contracts have also been adjusted to report their names as (and/c real? ...). This mostly is an improvement for contract-stronger, but also make it so that (between/c -inf.0 +inf.0) just uses the real? predicate directly, instead of a more complex function |
||
---|---|---|
.. | ||
file | ||
future | ||
generic | ||
help | ||
json | ||
launcher | ||
match | ||
openssl | ||
pkg | ||
racket | ||
setup | ||
stxparse | ||
syntax | ||
units | ||
utils | ||
xml | ||
info.rkt | ||
run-automated-tests.rkt | ||
stress.rkt | ||
zo-path.rkt | ||
zo-size.rkt |