12018-08-20 Myles C. Maxfield <mmaxfield@apple.com>
2
3 [WHLSL] Call expressions shouldn't have type arguments
4 https://bugs.webkit.org/show_bug.cgi?id=188770
5
6 Reviewed by NOBODY (OOPS!).
7
8 Call expressions only had type arguments for casts, becuase native types can have type arguments.
9 However, instead of putting those type arguments on the CallExpression, we should parse the casted
10 type as a real type and not as an identifier, which puts the type arguments in the TypeRef.
11
12 * WebGPUShadingLanguageRI/CallExpression.js:
13 (CallExpression):
14 (CallExpression.prototype.get name):
15 (CallExpression.resolve):
16 (CallExpression.prototype.get typeArguments): Deleted.
17 (CallExpression.prototype.becomeCast): Deleted.
18 * WebGPUShadingLanguageRI/NameResolver.js:
19 (NameResolver.prototype.visitCallExpression):
20 * WebGPUShadingLanguageRI/Parse.js:
21 (parseConstexpr):
22 (parseTypeDef):
23 (parseLeftOperatorCall):
24 (parseCallExpression.let.parseArguments):
25 (parsePossiblePrefix):
26 (parsePossibleRelationalEquality):
27 (parseLeftLogicalExpression):
28 (parseIfStatement):
29 (parseWhile):
30 (parseFor):
31 (parseDo):
32 * WebGPUShadingLanguageRI/RemoveTypeArguments.js:
33 * WebGPUShadingLanguageRI/Rewriter.js:
34 (Rewriter.prototype.visitCallExpression):
35