-
Notifications
You must be signed in to change notification settings - Fork 29
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
[WIKI]: Document using Source functions in modules #76
Comments
Is 'sicp' a module here? If yes then we can write something like |
Has this been adequately addressed by #192? |
I think yes. But is this documented anywhere? |
I am unsure if this has since been documented somewhere, but developers should now be able to see how to use real js-slang types and functions by referring to existing modules which have since adopted the new technology.
It is worth noting that if a file uses js-slang functions (excluding types - types appear to be ok), then that file must not be imported by any tab, or building will fail. This may or may not get addressed down the line, removed as a limitation via updates to the build system. Longer explanation: |
Feature
How can I use Source functions in the implementation of a module?
Maybe
import { array_length } from "sicp";
Checklist
The text was updated successfully, but these errors were encountered: