Allow the definition of external types in artic.#36
Open
m-kurtenacker wants to merge 9 commits intomasterfrom
Open
Allow the definition of external types in artic.#36m-kurtenacker wants to merge 9 commits intomasterfrom
m-kurtenacker wants to merge 9 commits intomasterfrom
Conversation
Syntax (for now): `type_ext <name> = { <arg>, ... };` where the
arguments are strings that are passed through to the thorin backend.
The implementation of this feature depends on the backend. For now, only
C supports this feature, and only a single argument is supported.
`type_ext bar = { "foo" };` will cause thorin to emit `typedef foo bar;`.
The type (`bar`) is opaque to artic and thorin. This feature is mainly
intended to interact with external APIs, not to extend the artic
programming language as a whole.
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
2 participants
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.
Relates to AnyDSL/thorin#183.
The syntax for these external types is
type_ext <NAME> = { <Options> };, with<Options>being a List of string literals. Back-end support is required for these types to work; and the back-end will define how the type is being interpreted.