Ticket #5 (closed defect: fixed)
Check that top level CAFs don't have side effects.
|Reported by:||benl||Owned by:||bens|
|Component:||Core Type Checker||Version:||0.1.2|
There is no implied order of evaluation for top level CAFS. Indeed, Core.Sequence rearranges them so that they can be initialised in the correct order.
Check that CAFs don't have side effects, and throw a type error if they do.