From: Eric Dobson (eric.n.dobson at gmail.com) Date: Sun Mar 31 17:44:54 EDT 2013 |
|
There have been a couple recent bug reports because certain features need a type, such as cast and define-predicate. I was wondering whether TR/no-check should check that the types are well formed, but not check that the expressions are well typed? I'm thinking this would be less surprising to users, but wondering whether users would expect that type definition errors to still work in TR/no-check.
Posted on the dev mailing list. |
|