Document motivation for bridge module #301
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
chinedufn
force-pushed
the
why-a-bridge-module
branch
from
9f83bf0 to
09e3dcb
Compare
This commit introduces documentation explaining why `swift-bridge` uses a bridge module design, as opposed to, say, a design where users annotate their types with proc macro attributes.
chinedufn
force-pushed
the
why-a-bridge-module
branch
from
09e3dcb to
201f17d
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.
This commit introduces documentation explaining why
swift-bridgeusesa bridge module design, as opposed to, say, a design where users
annotate their types with proc macro attributes.