That sounds great! Thank you for your consideration.
Best,
CG
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
After some discussion within R core, we decided that a "nomatch"
argument on regmatches() may be a good initial step. We might add a
new function later that combines the regexpr() and regmatches() steps.
The gregexpr() and regexec() inputs are both lists so it's not clear
whether a "nomatch" value
I think that's a good reason for not including this in regmatches; you're
right, its name is somewhat suggestive of yielding matches. Also, that sounds
like a great design for strcapture with an atomic prototype.
Best,
CG
__
R-devel@r-project.org mail
> From: William Dunlap [mailto:wdun...@tibco.com]
> Precedence is a property of the parser and has nothing to do with the
> semantics assigned to various symbols.
Yes, but output depends on evaluation as well as precedence. Seeing different
things wasn't an immediate surprise.
Your own parse(
Dear all,
`rbind()` returns a zero row data frame when binding zero column data
frames, see example below:
``` r
# a data frame with 1 row and 0 column
x <- data.frame(row.names=1)
x
#> data frame with 0 columns and 1 row
rbind(x,x)
#> data frame with 0 columns and 0 rows
```
I would have expect
On 8/31/19 12:35 AM, William Dunlap via R-devel wrote:
Prior to R-3.6.0 the keys in the lazyload key files, e.g.
pkg/data/Rdata.rdx or pkg/R/pkg.rdx, seemed to all be 2-long integer
vectors. Now they can be lists. The ones I have seen have two components,
"eagerKey" is a 2-long integer vector a
