[WGSL] Add support for calls with simple built-in types

[tadeuzagallo]

e511c23

[WGSL] Add support for calls with simple built-in types
https://bugs.webkit.org/show_bug.cgi?id=257028
rdar://109564906

Reviewed by Myles C. Maxfield.

Allow function calls with simple built-in types (i.e. function-style cast) such
as `f32(x)`. The way we currently handle it is not great, since we treat type
names as keywords in the lexer, but all of this will have to be refactored soon
when we update the parser to solve the template ambiguity. For now, this unblocks
a few more CTS tests to pass.

* Source/WebGPU/WGSL/Metal/MetalFunctionWriter.cpp:
(WGSL::Metal::FunctionDefinitionWriter::visit):
* Source/WebGPU/WGSL/Parser.cpp:
(WGSL::Parser<Lexer>::parsePrimaryExpression):

Canonical link: https://commits.webkit.org/264314@main

650d0c5

Misc	iOS, tvOS & watchOS	macOS	Linux	Windows
✅ 🧪 style	✅ 🛠 ios	✅ 🛠 mac	✅ 🛠 wpe	✅ 🛠 wincairo
	✅ 🛠 ios-sim	✅ 🛠 mac-AS-debug	✅ 🧪 wpe-wk2
✅ 🧪 webkitperl	✅ 🧪 ios-wk2	✅ 🧪 api-mac	✅ 🛠 gtk
	✅ 🧪 ios-wk2-wpt		✅ 🧪 gtk-wk2
	✅ 🧪 api-ios	✅ 🧪 mac-wk2	✅ 🧪 api-gtk
	✅ 🛠 tv	✅ 🧪 mac-AS-debug-wk2
	✅ 🛠 tv-sim
✅ 🛠 🧪 merge	✅ 🛠 watch
	✅ 🛠 watch-sim

[webkit-early-warning-system]

EWS run on current version of this PR (hash 650d0c5)

Misc	iOS, tvOS & watchOS	macOS	Linux	Windows
✅ 🧪 style	✅ 🛠 ios	✅ 🛠 mac	✅ 🛠 wpe	✅ 🛠 wincairo
	✅ 🛠 ios-sim	✅ 🛠 mac-AS-debug	✅ 🧪 wpe-wk2
✅ 🧪 webkitperl	✅ 🧪 ios-wk2	✅ 🧪 api-mac	✅ 🛠 gtk
	✅ 🧪 ios-wk2-wpt		✅ 🧪 gtk-wk2
	✅ 🧪 api-ios	✅ 🧪 mac-wk2	✅ 🧪 api-gtk
	✅ 🛠 tv	✅ 🧪 mac-AS-debug-wk2
	✅ 🛠 tv-sim
✅ 🛠 🧪 merge	✅ 🛠 watch
	✅ 🛠 watch-sim

[litherum]

Is this really the right way to do it? Users can create their own types, and their own types will have these kind of constructors too - but we can't literally list the user-defined types inside our WGSL compiler. I'd imagine both the user-defined type constructors and the primitive type constructors would be handled with the same infrastructure.

[tadeuzagallo]

No, this is isn't the right way to do it. But as I mentioned in the changelog, our whole definition of CallExpression needs to change, as we currently only allow types as the target, so this will all need to be refactored. I'm thinking that later we'll distinguish whether we're constructing a type or calling a function, and if we're constructing a type we can use the inferred type which would already account for any aliasing.

[webkit-commit-queue]

Committed 264314@main (e511c23): https://commits.webkit.org/264314@main

Reviewed commits have been landed. Closing PR #14076 and removing active labels.