Skip to content
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

Pragmas #750

Merged
merged 2 commits into from
Aug 31, 2024
Merged

Pragmas #750

merged 2 commits into from
Aug 31, 2024

Conversation

hishamhm
Copy link
Member

No description provided.

@Frityet
Copy link

Frityet commented Jun 15, 2024

Maybe this shouldn't be an error on unknown pragma? I see the value of some pre-processing tools having custom pragmas

@hishamhm
Copy link
Member Author

From a comment in #786

This might be useful to add as documentation at some point:

Also, the pragma proposal is not intended to double as annotations (the kinds of things you usually see with @- syntax in other languages). Pragmas are intended as compiler directives, more akin to compiler flags (e.g. the #pragma use in C compilers). I understand these sit in a gray area, but I don't think there's a well-established definition in the literature.

My practical goal for pragmas is to allow for handling compatibility issues when dealing with the language evolution. That is, in a Teal codebase with no legacy concerns, there should be no pragmas.

@hishamhm hishamhm merged commit 1b12d76 into next Aug 31, 2024
7 checks passed
@hishamhm hishamhm deleted the pragmas branch August 31, 2024 21:08
@hishamhm
Copy link
Member Author

Merged into next!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants