Permit zero-temporary-value buffer binding

[rbtcollins]

When using custom 3D renderers, p5 can support much larger models, but this particular bit of code showed up as a hotspot: I was passing in a Float32 already, and it was getting cloned.

Without this change, my particular workload runs at 7-12 fps. With it 45-50fps.

In principle p5 can make use of this itself, though having webGL ready representations as the source of truth is a much larger change - but even so, taking steps in that direction seems broadly useful.

Resolves #[Add issue number here]

Changes:

Screenshots of the change:

PR Checklist

• npm run lint passes
• Inline documentation is included / updated
• Unit tests are included / updated

Fixes: #5739

[welcome]

🎉 Thanks for opening this pull request! Please check out our contributing guidelines if you haven't already. And be sure to add yourself to the list of contributors on the readme page!

[Qianqianye]

Thank you @rbtcollins ! As a reminder, an issue needs to be opened before a pull request is opened, then you can tag the issue in the pull request. You can read more about it in the GitHub Issue Flow. This is necessary for tracking development and keeping discussion clear. I will close this PR for now for organizational purpose, and please feel free to open a new PR after an issue is opened. Thanks!

[rbtcollins]

@Qianqianye hoop jumped through, you should be able to re-open this PR now.

[davepagurek]

I'm going to close this PR for now because in the time since, we've started adding some tools to p5 to achieve something similar via p5.DataArray (and I think the else branch below also would let you do the workaround you mentioned where you manually replaced an array with a Float32Array):

p5.js/src/webgl/p5.RendererGL.js

Lines 1833 to 1837 in c06e12a

	if (values instanceof p5.DataArray) {
	data = values.dataArray();
	} else if (!(data instanceof (type || Float32Array))) {
	data = new (type || Float32Array)(data);
	}

I'm going to leave your issue open because we currently only internally use p5.DataArray for line data, which gets automatically created, so there's still some discussion to be had about the best way to do the same for developer-facing arrays like the vertices of a p5.Geometry. We'd love your feedback that if you have any ideas or opinions!