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

Define an "official" extension mechanism #38

Open
sampsyo opened this issue Oct 24, 2019 · 0 comments
Open

Define an "official" extension mechanism #38

sampsyo opened this issue Oct 24, 2019 · 0 comments

Comments

@sampsyo
Copy link
Owner

sampsyo commented Oct 24, 2019

Bril is supposed to be extensible, but that extensibility is currently pretty ad hoc: you just add whatever you want to the language. It would be nice to codify some standard way to package up extensions to Bril. There wouldn't need to be a machine-readable description of what an extension consists of, but maybe there should be a way in a Bril program to describe the extensions that the program relies on.

This would require that extensions get assigned (string) names. We would probably want to organize the documentation around a minimal "base" language and individual extensions.

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

No branches or pull requests

1 participant