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

Consider Mapping display, print, etc. to console.log? #337

Open
abhillman opened this issue Dec 12, 2023 · 1 comment
Open

Consider Mapping display, print, etc. to console.log? #337

abhillman opened this issue Dec 12, 2023 · 1 comment

Comments

@abhillman
Copy link

abhillman commented Dec 12, 2023

Perhaps one of the most basic operations one would wish to conduct after compiling a script is to print to console.log. At present, it appears that (#js*.console.log ...) must be used instead.

More generally, the problem to be solved here could be 'how can we write scripts that evaluate in both racketscript and racket (with respect to print)?'

It's possible that some function (macro?) could be introduced instead that would invoke print or #js*.console.log depending on the platform.

@abhillman abhillman changed the title Consider Mapping display, print, etc. to console.log Consider Mapping display, print, etc. to console.log? Dec 12, 2023
@abhillman
Copy link
Author

abhillman commented Dec 12, 2023

Short of some change to the language or additional code, some basic documentation that shows how to accomplish common JS operations in racketscript could be helpful.

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