feat: Automatically assign names to resources in Unplugin

[aleksanderkatan]

The high-level rule for autonaming is like this: if there is an assignment to a variable, we try to find one of the resourceConstructors among the identifiers in the assigned expression; if we succeed (and we don't find the $name identifier), we wrap the expression in a call to __TYPEGPU_AUTONAME__. If typegpu is initialized, this function checks if the expression has the $internal symbol, and names it (using $name) if it isn't already named.

I also needed to add [$internal]: true to some of the resources.

Let me know if I missed any of the resource generating functions.

[github-actions]

pkg.pr.new

packages

pnpm i https://pkg.pr.new/software-mansion/TypeGPU/typegpu@1344
pnpm i https://pkg.pr.new/software-mansion/TypeGPU/typegpu@24acc0cf048c67ae4ae1a735489952f93186ff51

benchmark
view benchmark

commit
view commit

[aleksanderkatan]

At least +500, -100 of these changes are tests :)

<moved to description>

[aleksanderkatan]

As of right now, functions marked with our directives are not assigned any names (no $name method, we need to save the names in the metadata). I decided to delegate that to another ticket: #1358

[reczkok]

At least +500, -100 of these changes are tests :)

The high-level rule for autonaming is like this: if there is an assignment to a variable, we try to find one of the resourceConstructors among the identifiers in the assigned expression; if we succeed (and we don't find the $name identifier), we wrap the expression in a call to __TYPEGPU_AUTONAME__. If typegpu is initialized, this function checks if the expression has the $internal symbol, and names it (using $name) if it isn't already named.

I also needed to add [$internal]: true to some of the resources.

Let me know if I missed any of the resource generating functions.

Please add that to the PR description

[mhawryluk]

Great job!! 🦾

[aleksanderkatan]

I added fn, vertexFn etc. to resourceConstructors. Now as a side effect shell creations are also wrapped in the autoname, but the reason for including this is so that TaggedTemplateExpressions, which don't fall under the shell calls category, are autonamed.

const myFn = tgpu['~unstable'].fn([Item], Item) /* wgsl */`(item: Item) -> Item { return item; }`;

[iwoplaza]

Amazing work, a great push forward! 👏👏👏

[iwoplaza]

Why this space here? 👀

Suggested change

	`) , ${metadata}) && $.f)({}))`,
	`), ${metadata}) && $.f)({}))`,