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.

Sign up for GitHub

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

Jump to bottom

Try out EVAL :compile-only #2819

Closed
coke opened this issue May 20, 2019 · 1 comment
Closed

Try out EVAL :compile-only #2819

coke opened this issue May 20, 2019 · 1 comment
Labels
wishlist "nice to have" issues; might require a lot of work or a big change or be low priority xt Regarding current or new xt/ tests or the utils/

Comments

@coke
Copy link
Collaborator

coke commented May 20, 2019

See rakudo/rakudo@d41f162

Might be possible to switch back to EVAL testing if this helps address the memory issue recently raised.
@coke coke added wishlist "nice to have" issues; might require a lot of work or a big change or be low priority xt Regarding current or new xt/ tests or the utils/ labels May 20, 2019
@coke coke self-assigned this May 20, 2019
@JJ
Copy link
Contributor

JJ commented May 20, 2019

That was pretty much fixed after the latest addition by @taboege. It's using a stable feature of NQP, which I guess is as stable (or not) as an experimental feature in current Rakudo master. Using that has got its disadvantages (like no error message if it fails, although that can be fixed easily), but speed and memory are both taken care of.

@coke coke removed their assignment Sep 27, 2019
@coke coke closed this as completed Feb 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
wishlist "nice to have" issues; might require a lot of work or a big change or be low priority xt Regarding current or new xt/ tests or the utils/
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JJ @coke