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 #937

Merged
merged 102 commits into from
May 7, 2022
Merged

Compiler #937

merged 102 commits into from
May 7, 2022

Conversation

ephread
Copy link
Collaborator

@ephread ephread commented Feb 19, 2022

Here we go, last stretch before the compiler lands in inkjs.

Previous discussion in #931.

Remaining tasks

  • Remove ink-proof and port the relevant tests from upstream. → @ephread
    • Ensure the tests run against the distributable .js files. → @smwhr
  • Add new tests checking that the JavaScript compiler generates the same JSON as inklecate. → @ephread
  • Disable float detection (for now), until we have settled on a solution (see [Compiler] Limitations regarding JavaScript's number type #934). → @smwhr
  • Put the runtime and the compiler in different namespaces to match upstream and unify shared types (e. g. ErrorType)
  • Review the entire port.
  • Investigate whether running ink-proof in the CI makes sense.

The fate of inklecate can be tackled at a later stage, until we figure out how we want to distribute it (per #933). Let's focus on releasing the compiler for now.

Checklist

  • The new code additions passed the tests (npm test).
  • The linter ran and found no issues (npm run-script lint).

Feel free to suggest more tasks or discuss them. If you want to contribute, call dibs and create a PR against the compiler branch.

@ephread
Copy link
Collaborator Author

ephread commented Feb 22, 2022

@y-lohse, @smwhr #939 is ready for review, feel free to assign yourselves \o/

@smwhr smwhr requested a review from y-lohse May 1, 2022 13:21
@y-lohse
Copy link
Owner

y-lohse commented May 7, 2022

Thank you once again for all the work that has gone into this 😍
I reviewed the config files, the tests and the engine changes… the compiler is too much code or me to review at this point, but I trust you 😊. Well you and the unit test suite haha.

I don't see any blockers, just 2 questions for double checking:

  1. The different tasks in the first comment are all actually done I believe?
  2. This PR doesn't introduce breaking changes to any of the public classes?

If we're good on these 2 points we can go ahead and merge this and release the new version as far as I'm concerned 🥳

@smwhr
Copy link
Collaborator

smwhr commented May 7, 2022

  1. The different tasks in the first comment are all actually done I believe?
  • tests checking that the JavaScript compiler generates the same JSON as inklecate : not automated but ran manually
  • runtime and the compiler in different namespaces : TBD
  1. This PR doesn't introduce breaking changes to any of the public classes?

No changes at all to what was already exposed.

I'm pressing merge ! 🥳

@smwhr smwhr merged commit 61b5263 into master May 7, 2022
@y-lohse y-lohse deleted the compiler branch May 7, 2022 12:50
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.

3 participants