We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Right now most buffer methods require manual passing of the stride of the buffer (eg. if it's a 2D points buffer or a 3D one).
An alternative approach would be to make 2 separate buffer entry points ( buffer2D, buffer3D ) but that feels overkill.
Composing buffers right now is confusing as you end up with a lot of stride repetition.
Babel macros might be an option, but that feels forced.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Right now most buffer methods require manual passing of the stride of the buffer (eg. if it's a 2D points buffer or a 3D one).
An alternative approach would be to make 2 separate buffer entry points ( buffer2D, buffer3D ) but that feels overkill.
Composing buffers right now is confusing as you end up with a lot of stride repetition.
Babel macros might be an option, but that feels forced.
The text was updated successfully, but these errors were encountered: