[bitc-dev] NOALLOC analysis

[Swaroop Sridhar]

Raoul Duke wrote:
>> types. But the subjective evidence from other languages that *do* have
>> effect types is that they very rapidly become an impediment to
>> usability, and I am very concerned that this might happen in BitC.
> 
> clueless question: can they be optional in the language? so that it is
> pay-as-you-go?

It is possible to add a switch to the compiler so that it will not
perform some of the effect checking (ex: alloc/noalloc), or make some
conservative default assumptions for the lack of programmer annotation.
However, code that must work in either mode (ex: libraries) must be
written in a fully annotated form.

Swaroop.