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

(tests) Implement more EvalHelper methods for compiled mode #463

Merged
merged 1 commit into from
Apr 23, 2024

Conversation

perlun
Copy link
Collaborator

@perlun perlun commented Apr 23, 2024

This is a preparation for removing interpreted mode completely, expected to follow shortly.

@perlun perlun added tests This issue is related to unit/integration tests experimental compilation Issues which are relevant when using experimental compilation labels Apr 23, 2024
perlun added a commit that referenced this pull request Apr 23, 2024
This has been an oversight while working on the experimental Perlang
compiler (#406). The bug
was discovered when implementing the changes in
#463; when we started running
one of those tests, no error was emitted even though the code was
redefining a top-level function. It turned out that the compiler would
silently overwrite a function if you defined it twice.
perlun added a commit that referenced this pull request Apr 23, 2024
This has been an oversight while working on the experimental Perlang
compiler (#406). The bug
was discovered when implementing the changes in
#463; when we started running
one of those tests, no error was emitted even though the code was
redefining a top-level function. It turned out that the compiler would
silently overwrite a function if you defined it twice.
@perlun
Copy link
Collaborator Author

perlun commented Apr 23, 2024

Failed in CI as expected, because we need the fix in #464 to make this work.

perlun added a commit that referenced this pull request Apr 23, 2024
This has been an oversight while working on the experimental Perlang
compiler (#406). The bug
was discovered when implementing the changes in
#463; when we started running
one of those tests, no error was emitted even though the code was
redefining a top-level function. It turned out that the compiler would
silently overwrite a function if you defined it twice.
@perlun perlun force-pushed the test/support-EvalHelper-methods-in-compiled-mode branch from 0314e01 to ab0f836 Compare April 23, 2024 20:50
@perlun perlun enabled auto-merge (squash) April 23, 2024 20:50
This is a preparation for removing interpreted mode completely, expected
to follow shortly.
@perlun perlun force-pushed the test/support-EvalHelper-methods-in-compiled-mode branch from ab0f836 to 383395c Compare April 23, 2024 20:56
@perlun perlun merged commit 783c5df into master Apr 23, 2024
14 checks passed
@perlun perlun deleted the test/support-EvalHelper-methods-in-compiled-mode branch April 23, 2024 21:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
experimental compilation Issues which are relevant when using experimental compilation tests This issue is related to unit/integration tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant