Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

WASM compilation #31

Closed
mrkmarron opened this issue Apr 18, 2019 · 2 comments
Closed

WASM compilation #31

mrkmarron opened this issue Apr 18, 2019 · 2 comments
Labels
design discussion Language design discussion issue enhancement New feature or request

Comments

@mrkmarron
Copy link
Contributor

Currently we have a simple (and poor performance) interpreter reference implementation. Having a WASM compiler target and runtime. This will also require some GC design (see issue #30) but it might be ok to start with a simple RC based design.
@mrkmarron mrkmarron added enhancement New feature or request design discussion Language design discussion issue labels Apr 18, 2019
@mrkmarron mrkmarron mentioned this issue May 5, 2019
Closed
@wandyezj
Copy link

wandyezj commented May 26, 2019 •
edited

Is it possible for Bosque programs to be a stricter set of existing TypeScript programs with additional libraries and for Bosque to translate to TypeScript? That way all the existing resources for TypeScript could be recycled, and libraries developed in Bosque could be easily consumed by existing TypeScript programs.

It would be nice to have strictly verified libraries for core functionality with looser rules for less core components in a program or website.

When developing compiler targets for Bosque, having a converter from TypeScript to Bosque would be pretty neat since it might allow many existing libraries to be quickly converted to support Bosque and other programming languages.

@mrkmarron
Copy link
Contributor Author

AOT compiler landing in master -- revisit this soon.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
design discussion Language design discussion issue enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wandyezj @mrkmarron