Argument named in breaks the in attriute in subsequent parameters (minor QoL thing)

[mid78000]

Declaring a parameter named in seems to be legal, but it can glitch the parser:

// works
[shader("vertex")]
FragIn vert(in OtherStuff o, in VertIn in)

// does not work
[shader("vertex")]
FragIn vert(in VertIn in, in OtherStuff o)

// works (but only because AFAIK "in" is the default)
[shader("vertex")]
FragIn vert(in VertIn in, OtherStuff o)

It looks like the name of parameter n affects how the annotations (or type name?) of parameters m > n are parsed, which doesn't seem like it should be a thing since those are different categories of identifier.

Not a blocker, more a QoL thing.