Move shared object exported entry points to tag dispatch #28
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
solidpixel
force-pushed
the
tag_dispatch2
branch
from
ac21e10 to
4dd1475
Compare
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.
The current code uses C++ template tag dispatch for the main layer intercept/driver dispatch function pointer tables, but not for the implementations backing the exported entrypoints. We currently emit per-layer code that is hard-coded to call "_default()" implementations. This is functional and allows replacement in the layer, but results in more code to maintain over the layers. We should just use the template tag dispatch mechanism everywhere.
Fixes #26 and #27