[sv-ac] Mantis 3202: $ function in classes & constraints, future $ value functions in 'let'

Hi guys-
I'm looking again at proposal 3202, where we had discussed extending the use of the various system functions to classes and constraints, and allowing future value functions in 'let'. I'm not sure I fully understand some of the issues here; can some of you clarify for me?

1. In the case of the bit vector functions ($countones, etc)-I didn't see any specific language (in the LRM or our 2476 proposal) that keeps them out of classes and constraints. Is there a reason people think they are currently prohibited there, or do we just need to clarify, perhaps with some additional examples, that they are not?

2. For the sampled value functions-was there a reason why we didn't want them in classes and constraints? Could we put language like, "These functions are allowed in any context in which their return type is valid"?

3. Similarly, if we want to allow future functions in 'let', could we add language like, "These are allowed in a let expression, provided that when it is instantiaed, the substituted expression is legal"?

Thanks!

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.