-
Notifications
You must be signed in to change notification settings - Fork 3k
Parse and use custom targets in exporters #4725
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
Parse and use custom targets in exporters #4725
Conversation
The actual |
@screamerbg FYI |
@theotherjimmy yes 👍 |
@theotherjimmy Who should review this change? |
Good question, @0xc0170. I don't know. Maybe @sarahmarshy? |
/morph export-build |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 83 All exports and builds passed! |
@adbridge LGTM! |
Resolves #4709
Also changes the API of the exporters to be more flexible WRT changes in
TARGET_MAP. The old API would pre-compute a supported list at import time.
This new API includes a class method for computing support for one target
or all targets. This might improve performace for single exports, as only
the current combination of support is checked instead of the whole matrix.