feat: `tgpu.resolveWithContext` - a tgpu.resolve alternative that returns used layouts and a catchall bind group, alongside code

[iwoplaza]

import tgpu from 'typegpu';
import { perlin3d } from '@typegpu/noise';

const root = tgpu.initFromDevice({ device });
const cache = perlin3d.staticCache({ root, size: d.vec3u(10, 10, 1) });

const { code, layouts, catchall } = tgpu.resolveWithContext({
  template: `
    fn main() {
      let value = perlin3d.sample(vec3f(0.5, 0., 0.));
      let wrappedValue = perlin3d.sample(vec3f(10.5, 0., 0.)); // the same as 'value'!
      // ...
    }

    // ...
  `,
  externals: { perlin3d },
});

[mhawryluk]

maybe tgpu.resolveWithResources?

[iwoplaza]

I like the suggestion! The resources part is a bit vague though. I guess we could go a few directions with the name:

• More specific to what the API does currently
  • ❌ I fear it could lock us out of returning more information from the API in the future
• A differentiation from the resolve API
  • ✅ If we don't focus on how it's different NOW, and just that it gives us more context about the resolution process, then these come to mind: resolveWithContext, resolveExtra, ???

What do you think?

[mhawryluk]

I like resolveWithContext!