You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In WebGPU we use this pattern to define a variable and an argumentdef entry at the same time:
<pre class=argumentdef for="GPU/requestAdapter(options)">
|options|: Criteria used to select the adapter.
</pre>
This doesn't work anymore with Bikeshed 5.0.0:
LINE 2271: Can't find the '|options|' argument of method 'GPU/requestAdapter(options)' in the argumentdef block.
Should Bikeshed support this or should we find an alternate pattern for WebGPU? (I like argumentdef because it shows optional/nullable, but otherwise would be perfectly happy to use <dl dfn-type=argument>.)
The text was updated successfully, but these errors were encountered:
Ah, that looks like an unintentional regression. I can run the parser over those bits.
Tho, what is the value of marking that as a var? At least in the example you provided here, it's not used in the argumentdef block, so it'll just be a "global" variable. (And if I ever add some auto-detection of var bounds when there's no algorithm attribute, it'll become an error since it's a variable that's never referenced a second time.)
It's kind of awkwardly displayed but it's used in the next block (the red one below the green one). It's also awkward because it's not possible to click on a var that's also a dfn, but once you find one of the other usages, it's possible to highlight them.
In WebGPU we use this pattern to define a variable and an argumentdef entry at the same time:
This doesn't work anymore with Bikeshed 5.0.0:
Should Bikeshed support this or should we find an alternate pattern for WebGPU? (I like argumentdef because it shows optional/nullable, but otherwise would be perfectly happy to use
<dl dfn-type=argument>
.)The text was updated successfully, but these errors were encountered: