search for: tidyeval

Displaying 9 results from an estimated 9 matches for "tidyeval".

2017 Mar 19
3
RFC: (in-principle) native unquoting for standard evaluation
Would this return a quosure? (i.e. a single sided formula that captures both expression and environment). That's the data structure we've adopted in tidyeval as it already has some built in support. Hadley On Friday, March 17, 2017, Michael Lawrence <lawrence.michael at gene.com> wrote: > Interesting idea. Lazy and non-standard evaluation is going to happen; the > language needs a way to contain it. > > I'll extend the proposal...
2017 Mar 17
4
RFC: (in-principle) native unquoting for standard evaluation
...the quoted variable name in-place, to allow more flexibility of NSE functions within a programming context. This mechanism exists within MySQL [3] (and likely other languages) and could potentially be extremely useful. Several alternatives have been incorporated into packages (most recently work on tidyeval) none of which appear to fully match the simplicity of the above, and some of which cut a forceful path through the syntax tree. The exact syntax isn't my concern at the moment (@ vs unquote() or other, though the first requires user-supplied native prefix support within the language, as per [...
2017 Mar 19
0
RFC: (in-principle) native unquoting for standard evaluation
...could come up with something. Michael On Sat, Mar 18, 2017 at 7:39 PM, Hadley Wickham <h.wickham at gmail.com> wrote: > Would this return a quosure? (i.e. a single sided formula that captures both > expression and environment). That's the data structure we've adopted in > tidyeval as it already has some built in support. > > Hadley > > > On Friday, March 17, 2017, Michael Lawrence <lawrence.michael at gene.com> > wrote: >> >> Interesting idea. Lazy and non-standard evaluation is going to happen; the >> language needs a way to contain...
2017 Mar 19
3
RFC: (in-principle) native unquoting for standard evaluation
Michael Lawrence (as last in long series of posters)... > Yes, it would bind the language object to the environment, like an > R-level promise (but "promise" of course refers specifically to just > _lazy_ evaluation). > > For the uqs() thing, expanding calls like that is somewhat orthogonal > to NSE. It would be nice in general to be able to write something like >
2017 Mar 17
2
RFC: (in-principle) native unquoting for standard evaluation
...the quoted variable name in-place, to allow more flexibility of NSE functions within a programming context. This mechanism exists within MySQL [3] (and likely other languages) and could potentially be extremely useful. Several alternatives have been incorporated into packages (most recently work on tidyeval) none of which appear to fully match the simplicity of the above, and some of which cut a forceful path through the syntax tree. The exact syntax isn't my concern at the moment (@ vs unquote() or other, though the first requires user-supplied native prefix support within the language, as per [...
2017 Mar 17
0
RFC: (in-principle) native unquoting for standard evaluation
...name in-place, to allow more flexibility of NSE functions > within a programming context. This mechanism exists within MySQL [3] (and > likely other languages) and could potentially be extremely useful. Several > alternatives have been incorporated into packages (most recently work > on tidyeval) none of which appear to fully match the simplicity of the > above, and some of which cut a forceful path through the syntax tree. > > The exact syntax isn't my concern at the moment (@ vs unquote() or other, > though the first requires user-supplied native prefix support within the...
2017 Mar 19
0
RFC: (in-principle) native unquoting for standard evaluation
...al, though without tracking down > all the tweets, etc. that are referenced. I suspect I'm not the only > reader who isn't clear exactly what is being proposed. I think a > detailed, self-contained proposal would be useful. We have a working implementation (which I'm calling tidyeval) in https://github.com/hadley/rlang, but we have yet to write it up. We'll spend some time documenting since it seems to be of broader interest. > One thing I'm not clear on is whether the proposal would add anything > semantically beyond what the present "eval" and "s...
2017 Sep 07
0
Revolutions blog: August 2017 roundup
...com/2017/08/buzzfeed-plane-tracking.html Timo Grossenbacher offers a helpful workflow for implementing reproducible data analysis in R: http://blog.revolutionanalytics.com/2017/08/reproducibility-a-cautionary-tale.html A preview of version 0.10.0 of the dplyrXdf package, featuring support for the tidyeval framework on out-of-memory Xdf data files: http://blog.revolutionanalytics.com/2017/08/dplyrxdf-0100-beta-prerelease.html A tutorial on using CNTK via the keras package for forecasting: http://blog.revolutionanalytics.com/2017/08/keras-and-cntk.html Neils Berglund explains how to use the sqlrutil...
2017 May 09
3
A few suggestions and perspectives from a PhD student
Hi, On 08/05/17 16:37, Ista Zahn wrote: > One of the key strengths of R is that packages are not akin to "fan > created mods". They are a central and necessary part of the R system. > I would tend to disagree here. R packages are in their majority not maintained by the core R developers. Concepts, features and lifetime depend mainly on the maintainers of the package (even