-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
Compiler Support #206
Comments
Duplicate issue (#181). |
🧠 |
Extensions can access the compiler already (and they are soon to be "supported"), but you won't receive any help with them. Extensions are designed in such a way that you aren't supposed to need to access the compiler, because if you were able to it'd suddenly become 2 extensions essentially, which means 2 environments all the blocks have to be tested in, and it becomes double the work. With how they're written at the moment, all the functions and such are verified to work in both the interpreter and the compiler and there's not much need to test each environment, except some rare cases. Some extensions have blocks that genuinely cannot work without access to the compiler and in those cases, said exports do exist. However they don't come with documentation nor instruction on how to use them, and if they break, that's your fault. |
Let extensions access the compiler.
like this:
The text was updated successfully, but these errors were encountered: