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
Currently, slots throw when called from JS. We'd like to lift that restriction, we talk about the exact mechanism after App.js
Should accessors be accessible in "normal" mode?
There are cases where the contents of an accessor are accessible in normal mode (they aren't tied to a GPU resource like a buffer). The simplest cases are literals (.with(fooAccess, 15)) and constants (.with(fooAccess, foo)), the gray area are functions. Do we call them in JS?
In cases where accessors aren't accessible in JS, should we error the user using the accessor in JS, or should we error when providing a value that isn't accessible in JS.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, slots throw when called from JS. We'd like to lift that restriction, we talk about the exact mechanism after App.js
Should accessors be accessible in "normal" mode?
There are cases where the contents of an accessor are accessible in normal mode (they aren't tied to a GPU resource like a buffer). The simplest cases are literals (
.with(fooAccess, 15)) and constants (.with(fooAccess, foo)), the gray area are functions. Do we call them in JS?In cases where accessors aren't accessible in JS, should we error the user using the accessor in JS, or should we error when providing a value that isn't accessible in JS.
Beta Was this translation helpful? Give feedback.
All reactions