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

Compiler Support #206

Closed
0832k12 opened this issue Apr 21, 2024 · 3 comments
Closed

Compiler Support #206

0832k12 opened this issue Apr 21, 2024 · 3 comments

Comments

@0832k12
Copy link

0832k12 commented Apr 21, 2024

Let extensions access the compiler.
like this:
image
image

@FurryR
Copy link

FurryR commented Apr 21, 2024

Duplicate issue (#181).
Maybe you can ask for more exports.

@0832k12 0832k12 closed this as completed Apr 23, 2024
@0832k12
Copy link
Author

0832k12 commented Apr 23, 2024

🧠

@LilyMakesThings
Copy link

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.

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

3 participants