Refactor uneval into separate package. #115

jamiefolson opened this Issue Nov 19, 2012 · 1 comment

2 participants


In running headlong into the brick wall of getting unevaluated arguments passed through to S4 methods, I came across the following thread:

It was suggested there that the uneval-related functions in plyr be migrated to a separate package. This struck me as a great idea seeing how much harder it is to have function arguments implicitly used as unevaluated expressions.



I'd be happy to accept a patch, but it's not high on my to do list.

@hadley hadley closed this Jan 2, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment