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

When package code is executed and the implications #550

Closed
jennybc opened this issue Apr 8, 2019 · 1 comment · Fixed by #659
Closed

When package code is executed and the implications #550

jennybc opened this issue Apr 8, 2019 · 1 comment · Fixed by #659

Comments

@jennybc
Copy link
Collaborator

jennybc commented Apr 8, 2019

Capturing enough from a recent Slack conversation that we don't forget this ...

Have a nice table with R CMD build, R CMD INSTALL, library(pkg) and pkg::fun() and then showing what code is executed for each

Context: appreciating build-time dependencies (r-lib/devtools#1788) or, more generally, build-time definitions (could also be data, such as crayon's regrettable caching of color capabilities at build time).

cc @gaborcsardi

@jennybc
Copy link
Collaborator Author

jennybc commented Apr 8, 2019

Example: you want to express "let my foo be their foo". These are more different than you might think:

foo <- pkgB::foo

vs

foo <- function(...) pkgB::foo(...)

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 a pull request may close this issue.

1 participant