Contents

- maybe make some screencasts

- you can now do something like Haskell's quickcheck. Every contract has a method 'test_data' or something. You can use that data to automatically check methods with contracts to make sure they are correct.
  - http://www.cse.chalmers.se/~rjmh/QuickCheck/manual.html
  - for stuff like the Not contract, should I make a standard set of classes to check those functions with? Would that be useful at all?
  - also write specs for this stuff

Version data entries

38 entries across 29 versions & 6 rubygems

Version	Path
contracts-0.17.2	TODO.markdown
contracts-0.17.1	TODO.markdown
entitlements-app-1.1.0	lib/contracts-ruby3/TODO.markdown
entitlements-app-1.1.0	lib/contracts-ruby2/TODO.markdown
entitlements-app-1.0.0	lib/contracts-ruby2/TODO.markdown
entitlements-app-1.0.0	lib/contracts-ruby3/TODO.markdown
entitlements-app-0.3.4	lib/contracts-ruby3/TODO.markdown
entitlements-app-0.3.4	lib/contracts-ruby2/TODO.markdown
entitlements-app-0.3.1	lib/contracts-ruby3/TODO.markdown
entitlements-app-0.3.1	lib/contracts-ruby2/TODO.markdown
entitlements-app-0.3.0	lib/contracts-ruby3/TODO.markdown
entitlements-app-0.3.0	lib/contracts-ruby2/TODO.markdown
entitlements-0.2.1	lib/contracts-ruby3/TODO.markdown
entitlements-0.2.1	lib/contracts-ruby2/TODO.markdown
entitlements-app-0.2.1	lib/contracts-ruby2/TODO.markdown
entitlements-app-0.2.1	lib/contracts-ruby3/TODO.markdown
entitlements-0.2.0	lib/contracts-ruby3/TODO.markdown
entitlements-0.2.0	lib/contracts-ruby2/TODO.markdown
entitlements-app-0.2.0	lib/contracts-ruby2/TODO.markdown
entitlements-app-0.2.0	lib/contracts-ruby3/TODO.markdown