New issue
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
Wrong VertexLayoutBuilder semantics #10
Comments
Thanks for the report. The way While I will accept a PR for this, I will likely need to re-implement it later on in the generator. |
Unfortunately even if I fix the bindgen repo to not use hard-coded paths it's still panicking, and I don't really want to look further into that. I'll fix it in here for now. |
Yes that is fine. I'm planning to remove the hard coding + some cleanup to the code, but I just haven't gotten around to do it |
@BenjaminSchaaf hey, just FYI 0.15 has been released which includes your changes (and also BGFX updated to latest version) |
@emoon Awesome, thanks :) |
I encountered some crashes/invalid rendering when using multiple
VertexLayoutBuilder
. I narrowed this down toVertexLayoutBuilder.end()
not being called by me, but in doing so I found numerous issues withVertexLayoutBuilder
:begin
,add
andend
mutate the builder but don't take a mutable referenceVertexLayoutBuilder
is able to be passed to various APIs withoutend
being called. A new type safely encapsulating this requirement would be preferred.begin
andadd
both return&Self
, meaning you can't assign their result to a variable. AFAIKSelf
is idiomatic.I'm working on a PR for this.
The text was updated successfully, but these errors were encountered: