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
I like this glsl() babel preprocessor idea and I wanted something similar, not only to work with glslify but also to have something that can statically extract out the uniform types (so I can do code optim without need to resolve them at runtime) as well as providing a better error feedback to user.
What do you think of this idea? Could glsl() not yield a string, but instead an object with { code, types }.
An other idea I had, a bit more advanced, is that having the type at compile time could help js type languages like flowtype or typescript.
The text was updated successfully, but these errors were encountered:
I like this glsl() babel preprocessor idea and I wanted something similar, not only to work with glslify but also to have something that can statically extract out the uniform types (so I can do code optim without need to resolve them at runtime) as well as providing a better error feedback to user.
What do you think of this idea? Could glsl() not yield a string, but instead an object with
{ code, types }
.An other idea I had, a bit more advanced, is that having the type at compile time could help js type languages like flowtype or typescript.
The text was updated successfully, but these errors were encountered: