It now correctly errors when parsing 'x y', instead of parsing it as 'y' as it previously did