AST compiling failling with an array without member rules about dry-types HOT 3 CLOSED

We should handle this use case, but I gotta ask - why the array elements "don't matter"? What I'm trying to do with these libs is to make people concious about type safety in a rather strict way. If you're using these libs to handle input from "the outside world" then you should be conservative about type expectations. I also understand that these libs might be used in contexts where less strict approach is fine, so I'm wondering what's your use case now :)

from dry-types.

I was thinking about that too, I think that we will always care about the contents of an array in some way. My real use case was that each itself wasn't checking before hand if something was an array and blew up when calling map, that's why I wanted to set the :array? rule there, but it then throw that error.

Maybe we should raise a more meaningful exception when someone is trying to use :array? without member rules? Or just let it be?

from dry-types.

This is now fixed in master. I'll push 0.8.1 later today.

from dry-types.