My own hammock time on this led me to believe that in most cases where users care about what uris they are testing, a custom generator will be required. There are very few applications that actually expect a wide variety of uri forms, so I saw no point in spending a lot of effort in producing them. Instead I picked the most likely uri form people expect to see.
Similarly, building a growing, widely random set of urls that still match the spec is itself a fun project. I saw no point in building that though if, again, people will need to override it anyways. If you want to build a really amazing shrinking uri generator, I would recommend doing so in test.check so that we can use it from core. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
