Skip to content

/ vetr

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

Jump to bottom

Deal with funky UNPROTECT/PROTECT in evaluate_recurse #73

Closed
brodieG opened this issue Aug 25, 2017 · 0 comments
Closed

Deal with funky UNPROTECT/PROTECT in evaluate_recurse #73

brodieG opened this issue Aug 25, 2017 · 0 comments
Labels
bug fixed in dev
Milestone
0.2.0

Comments

@brodieG
Copy link
Owner

@brodieG brodieG commented Aug 25, 2017

This is because we need to protect input to ALIKEC_internal, but then don't want the input on the stack after that, and we need to protect the output.
@brodieG brodieG added the bug label Aug 25, 2017
@brodieG brodieG added this to the 0.1.1 milestone Aug 25, 2017
@brodieG brodieG added the fixed in dev label Sep 3, 2017
@brodieG brodieG closed this in e6c3420 Sep 17, 2017
brodieG added a commit that referenced this issue Sep 17, 2017
@brodieG
v0.2.0 release to CRAN
Loading status checks…
eba8694 
Fix #81, Fix #77, Fix #76, Fix #73, Fix #70,
Fix #69, Fix #65, Fix #64, Fix #61, Fix #59
Fix #56, Fix #51, Fix #48, Fix #47, Fix #46,
Fix #45, Fix #43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug fixed in dev
Projects
None yet
Milestone
0.2.0
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
@brodieG
You can’t perform that action at this time.