It's a bad idea. See, even if a constraint is not satisfied, there is no reason why it can't be satisfied later, in another module. So, inclusion of another module might change the behaviour of the code that was already compiled. I'm sure that after some oleging you'd find something that is more or less similar to what you want, but it's still a bad idea. 16.10.2014, 14:58, "Ivan Lazar Miljenovic" :

Using the Constraint type and the ConstraintKinds extension, is there any way we can determine if a Constraint is satisfied (i.e. a type-level function of type Constraint -> Bool using DataKinds)?

-- Ivan Lazar Miljenovic Ivan.Miljenovic@gmail.com http://IvanMiljenovic.wordpress.com _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

On Oct 16, 2014, at 6:58 AM, Ivan Lazar Miljenovic wrote:

Using the Constraint type and the ConstraintKinds extension, is there any way we can determine if a Constraint is satisfied (i.e. a type-level function of type Constraint -> Bool using DataKinds)?

No, for precisely this reason: On Oct 16, 2014, at 7:06 AM, Miguel Mitrofanov wrote:

See, even if a constraint is not satisfied, there is no reason why it can't be satisfied later, in another module. So, inclusion of another module might change the behaviour of the code that was already compiled.

But I disagree here:

I'm sure that after some oleging you'd find something that is more or less similar to what you want, but it's still a bad idea.

If you figure out some way to encode the feature you're after (converting a Constraint to a Bool like this), you've broken the type system. Please submit a bug report! Thanks, Richard