Array-based function pointer tables #408
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bromeon
added
quality-of-life
…ed fields Should reduce the amount of generated code and thus compile time, while providing the same functionality. This is not yet done for utility functions and builtin lifecycle methods, as those have a higher chance of being used via names, and they are not that big in comparison.
Bromeon
force-pushed
the
qol/indexed-method-tables
branch
from
1fc5a9b
to
960dae6
Compare
|
API docs are being generated and will be shortly available at: https://godot-rust.github.io/docs/gdext/pr-408 |
|
API docs are being generated and will be shortly available at: https://godot-rust.github.io/docs/gdext/pr-408 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Class and builtin function tables now use giant arrays instead of named fields.
Reduces the amount of generated code and thus compile time, while providing the same functionality. In particular, this should address the clippy issue.
Utility functions and builtin lifecycle methods still keep named method tables, as those have a higher chance of being used via names, and they are not that big in comparison.