Enable processing for all abstracts. #291
Draft
+61
−57
Conversation
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
|
I've noticed that explicitly excluding the Also, while I'm at it, you might wanna remove the |
Member
Author
My initial theory is that these are all enum abstracts, and in the compiled code these values get inline replaced, so we'd have to make a separate implementation to handle them. |
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.
Work in progress to enable processing on every abstract instead of just FlxColor.
Draft because whenever I try to build with this, I get the
(unknown position) Type Not Found: Terror, which implies it's trying to process a generic type somewhere, but since I don't know what type it's trying to process, I can't resolve the issue.TODO: Try restricting by package, and see if I can narrow down the culprit that way?