Type definitions should not be accepted after value definitions

[MartinErwig]

Type definitions should not be accepted after the first value definition. E.g., the following program should be rejected by the parser.

game Error_TypeDefinitionAfterValueDefinition

x : Int
x = 3

type Foo = {A,B}

y : Foo
y = A

[montymxb]

For whoever is interested it would be worth looking at Parser.hs 477-479. This allows declarations to be mixed with type defs. Removing the type defs here would prevent this from happening, but one would also need to make sure type defs can follow an input type def as seen in Parser.hs 528.