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

Switch to promise based execution model #1

Merged
merged 2 commits into from
Jan 27, 2018
Merged

Switch to promise based execution model #1

merged 2 commits into from
Jan 27, 2018

Conversation

RauliL
Copy link
Owner

@RauliL RauliL commented Jan 27, 2018

It's 2018, so non-asynchronous components won't work very well with modern JavaScript API's. While the synchronous execution model has worked very well in the past, attempting to include it in a browser and then using promise based API's such as fetch won't work very well.

As an experiment, convert the entire execution model of the interpreter into asynchronous promise based one.

It's 2018, so non-asynchronous components won't work very well with
modern JavaScript API's. While the synchronous execution model has
worked very well in the past, attempting to include it in a browser and
then using promise based API's such as `fetch` won't work very well.

As an experiment, convert the entire execution model of the interpreter
into asynchronous promise based one.
Add required infrastructure to run automated tests in CI and report test
coverage.
@RauliL RauliL merged commit 91aeb95 into master Jan 27, 2018
@RauliL RauliL deleted the promises branch January 27, 2018 15:29
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

Successfully merging this pull request may close these issues.

None yet

1 participant