Conversation
Member
|
I guess we still need int in there for old code? is this correct? |
Member
Author
|
The typeset has the older int prototype, this shouldn’t break anything older. Many of our built-in plugins still use the |
Member
|
Why not just change it to any then? Does this give some micro-optimization? |
Member
Author
|
@KyleSanderson if we changed |
asherkin
approved these changes
Jul 25, 2018
This file contains hidden or 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
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.
Native callbacks currently require plugin authors to retag their returns to an
int, but by addinganyas another acceptable prototype we allow them to return without needing to retag.Thanks asherkin for bringing this change to light