[Types-sig] updated proposal

[Tony Lownds]

On http://www.lyra.org/greg/python/typesys/type-proposal.html:
> Typedefs
> 
[...]
>
> Question: 
>      typedecl allows for an 'or' between items in the declarator. Does
> this create parsing problems with the 'or' in a test rule? For example,
> will the following be unambiguous to the
>      parser: 
> 
>           a = typedef Int or String
> 
>      How will the parser bind it? 
>           (typedef Int) or String 
>           (typedef Int or String) 
> 

I tried the typedef syntax and tested it and the answer is (typedef Int or
String). 

From Greg's email titled "[Types-sig] parameterization and syntax": 
> [ I just realized that: x = y ! SomeType(Int) has similar binding
>   precedence issues. is (y!SomeType)(Int) or y!(SomeType(Int)) ]

I tried this too; it binds as y!(SomeType(Int))

-Tony