Dear list,
This is a follow-up with another potential improvements of ave.
In the doc, x is documented as to be "a numeric", but this is not mandatory.
DF <- data.frame(x = letters, group = rep(1:2, each = 13))
ave(DF$x, DF$group, FUN = function(i) "a")
# [1] "a" "a" "a" "a" "a" "a" "a"
> On Apr 17, 2021, at 5:52 AM, Ivan Krylov wrote:
>
> On Sat, 17 Apr 2021 00:13:42 +
> Ryan Novosielski wrote:
>
>> reg-tests-1d.Rout.fail:
>> https://rutgersconnect-my.sharepoint.com/:u:/g/personal/novosirj_oarc_rutgers_edu/EYK2JHWQ1-9Dvu6gK9lrkRIBkEyA4QqkeH7C4gmbAYyBBQ?e=lfGJL7
>> reg-pac
No. We need more time to resolve issues revealed in testing.
Best,
luke
On Sat, 17 Apr 2021, Brenton Wiernik wrote:
Is the pipe bind `=>` operator likely to be restored by default in time for the
4.1 release?
Brenton
[[alternative HTML version deleted]]
__
Is the pipe bind `=>` operator likely to be restored by default in time for the
4.1 release?
Brenton
[[alternative HTML version deleted]]
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Thank you Ryan and Ivan for reporting and debugging this. Godbolt.org
shows that icc 19.0.1 with -O2 -ipo (inter-procedural optimizations) is
too smart and optimizes this stack growth detection code so that it
returns incorrect result on x86_64. Detecting stack growth from C is
tricky - in prin
Dear Deepayan,
I do not have further suggestions, but I just wanted to thank you for taking
the time to improve the documentation so much! (and for adding support for
specifying "varying" as a vector)
Both "Typical usage" and the details are useful additions. Adding a vignette
also seems an ex
On Sat, 17 Apr 2021 00:13:42 +
Ryan Novosielski wrote:
> reg-tests-1d.Rout.fail:
> https://rutgersconnect-my.sharepoint.com/:u:/g/personal/novosirj_oarc_rutgers_edu/EYK2JHWQ1-9Dvu6gK9lrkRIBkEyA4QqkeH7C4gmbAYyBBQ?e=lfGJL7
> reg-packages.Rout.fail:
> https://rutgersconnect-my.sharepoint.com/:u:
On Fri, 16 Apr 2021 18:39:04 +
Ryan Novosielski wrote:
> I guess there’s probably some mode of m4 I could run against that and
> see if there’s any indication?
Here's a shell script that should be doing the same thing that
R's .../configure does, but a bit more verbose:
Just for completeness, This can be easily illustrated simply in R, no C code
needed:
cat("foo\n\rbar\n")
In unix terminal:
> cat("foo\n\rbar\n")
foo
bar
In Mac-GUI:
> cat("foo\n\rbar\n")
bar
Cheers,
Simon
> On Apr 17, 2021, at 20:29, Simon Urbanek wrote:
>
> Ah, so you're not using R
Ah, so you're not using R console, you're using the R.app Mac-GUI. That one is
not a terminal, so it has entirely different rules, because it is combining all
four streams (stdout, stderr and WriteConsole for both output and message).
Also for historical reasons macOS (the original) used to us
Hi Simon,
Thank you for the feedback.
It is really strange that you have a different output.
I have attached a picture of my R console.
I am just trying to port some pure C code that prints progress bars to R
but it does not seem to be printing properly.
It seems I am doing something wrong with REp
11 matches
Mail list logo
