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

isolate .libPaths() down function calls #212

Open
maxheld83 opened this issue May 23, 2019 · 0 comments
Open

isolate .libPaths() down function calls #212

maxheld83 opened this issue May 23, 2019 · 0 comments
Milestone

Comments

@maxheld83
Copy link
Owner

this would extend #207 and #211, where currently we can toggle between different library paths within the same script, but not within the same call, where say, level 1 of the stack trace uses foo from R_LIBS_WORKFLOW and level 2 and down uses R_LIBS_ACTION or something similar.

Not even remotely aware whether this is possible, but it would be neat.

The problem arises when the "worker" function (say, desc as a dep of covr is also called in a different version by foo, while foo is run as part of covr).

Very deep backlog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant