id	summary	reporter	owner	description	type	status	priority	milestone	version	resolution	keywords	cc
19	SPEC interferes with optimisations	rl		Since SPEC is a sum type and we immediately inspect it in a loop, the demand analyser can't infer the strictness of the other loop arguments. Perhaps seq on it instead of pattern matching? Originally spotted while working on #18.	defect	closed	critical	0.7	0.6	fixed