search

ifigueroap / racket-quickcheck

Quickcheck Clone implemented in Racket
Other
32 stars 16 forks source link

Avoid `check` conflict with RackUnit #11

Closed ifigueroap closed 9 years ago

ifigueroap commented 9 years ago

I think it is necessary to avoid conflicts with RackUnit, namely the export of the check symbol. In the end, the only difference between check and quickcheck is the config argument. Therefore we could have a naming convention like:

quickcheck : the default quick config quickcheck/config: the check that takes an explicit config.

Then in the yet-to-be-implemented quickcheck-rackunit integration package we can define check-property and check-property/config as suggested by @jackfirth

What do you think?

jackfirth commented 9 years ago

This naming works very well, since a/b is pronounced "a with b" in scheme naming conventions. Definitely a good idea.