Proposal: split clojure.test.check.random namespace into separate org.clojure/core.random library

127 views
Skip to first unread message

Sam Estep

unread,
Jun 11, 2017, 8:09:39 PM6/11/17
to Clojure Dev

As per the discussion here, I propose that the clojure.test.check.random namespace in the org.clojure/test.check library be split into its own separate library, to allow its API to be solidified for use in other contexts besides the test.check implementation.

In a comment on that Stack Overflow question, gfredericks mentioned that the scope of the library would need to be decided before such a split could occur. I am unsure of what the best decision would be in this case; thoughts?

Alex Miller

unread,
Jun 11, 2017, 10:41:03 PM6/11/17
to cloju...@googlegroups.com
Another related aspect here is whether core itself should support customizable rand sources:




On Sun, Jun 11, 2017 at 7:09 PM, Sam Estep <samuel...@gmail.com> wrote:

As per the discussion here, I propose that the clojure.test.check.random namespace in the org.clojure/test.check library be split into its own separate library, to allow its API to be solidified for use in other contexts besides the test.check implementation.

In a comment on that Stack Overflow question, gfredericks mentioned that the scope of the library would need to be decided before such a split could occur. I am unsure of what the best decision would be in this case; thoughts?

--
You received this message because you are subscribed to the Google Groups "Clojure Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure-dev+unsubscribe@googlegroups.com.
To post to this group, send email to cloju...@googlegroups.com.
Visit this group at https://groups.google.com/group/clojure-dev.
For more options, visit https://groups.google.com/d/optout.

Sam Estep

unread,
Jun 12, 2017, 8:46:45 AM6/12/17
to Clojure Dev

I would not be opposed to including the functionality from clojure.test.check.random in core, if that’s what you mean. However, unless I misunderstand, it looks like that JIRA ticket may be orthogonal to this topic, as it would not support the purely functional, splittable RNGs in clojure.test.check.random, because the existing random functionality in clojure.core appears to depend on the mutability of the underlying RNG.

On Sunday, June 11, 2017 at 10:41:03 PM UTC-4, Alex Miller wrote:

Another related aspect here is whether core itself should support customizable rand sources:



On Sun, Jun 11, 2017 at 7:09 PM, Sam Estep <samuel...@gmail.com> wrote:

As per the discussion here, I propose that the clojure.test.check.random namespace in the org.clojure/test.check library be split into its own separate library, to allow its API to be solidified for use in other contexts besides the test.check implementation.

In a comment on that Stack Overflow question, gfredericks mentioned that the scope of the library would need to be decided before such a split could occur. I am unsure of what the best decision would be in this case; thoughts?

--
You received this message because you are subscribed to the Google Groups "Clojure Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure-dev...@googlegroups.com.

Reply all
Reply to author
Forward
0 new messages