@gfredericks are you aware that gen/list does not seem to be "just like gen/vector" in the sense that min and max arguments are not accepted?
also, why does gen/double* accept its min and max as keys in an opts map rather than flat args as gen/vector does ?
1) yes; gen/list is a bit second-class; I'm happy to take a patch for the docstring if it's misleading. I'd consider enhancing it to be like gen/vector, but that gets to
2) wherein the API is inconsistent, which is due to its being created in phases. I think opt maps everywhere would be ideal, and I suppose now that you have me thinking about it, gen/vector in particular could be evolved that way backwards compatibly
ok, cool. just wanted to make you aware (if not already)
[not a huge deal to me personally but yea of course consistency is good where possible]