Kurt,
Cool idea and great "seeing new faces" on here proposing things on here and
engaging with R-core on here.
Some comments on the issue of fallbacks below.
On Wed, Mar 27, 2019 at 10:33 PM Kurt Van Dijck <
dev.k...@vandijck-laurijssen.be> wrote:
> Hey,
>
> In the meantime, I submitted a bug
Hey,
In the meantime, I submitted a bug. Thanks for the assistence on that.
>and I'm not convinced that
>coercion failures should fallback gracefully to the default.
the gracefull fallback:
- makes the code more complex
+ keeps colConvert implementations limited
+ requires the user to on
I read through the editorial.
This is the one of the most mega-ultra-super-biased articles I've ever read.
e.g.
The authors encourage Baysian methods, and literally encourage subjective
approaches.
However, there's only one reference to robust methods and one reference to
nonparametric methods, bo
Thank you Tomas.
For the record, I'm confirming that the stray background R worker
process now times out properly after 'setup_timeout' (= 120) seconds:
{0s}$ Rscript -e 'parallel::makeCluster(1L, port=80)'
Error in socketConnection("localhost", port = port, server = TRUE,
blocking = TRUE, :
c
Could this be related to
"SIGNIFICANT USER-VISIBLE CHANGES
The default method for generating from a discrete uniform distribution
(used in sample(), for instance) has been changed. This addresses the
fact, pointed out by Ottoboni and Stark, that the previous method made
sample() noticeably non-un
I'm getting ready to submit an update of survival, and is my habit I run the
checks on all
packages that depend/import/suggest survival. I am getting some very odd
behaviour wrt
non-reproducability. It came to a head when some things failed on one machine
and worked
on another. I found t
> the prison made by ancient design choices
That prison of ancient design choices isn't so bad.
I have no further comments on object oriented semantics.
However, I'm planning to follow the following design pattern.
If I set the class of an object, I will append the new class to the
existing clas
Just to clarify/amplify: on the bug tracking system there's a
drop-down menu to specify severity, and "enhancement" is one of the
choices, so you don't have to worry that you're misrepresenting your
patch as fixing a bug.
The fact that an R-core member (Michael Lawrence) thinks this is
worth
This has some nice properties:
1) It self-documents the input expectations in a similar manner to
colClasses.
2) The implementation could eventually "push down" the coercion, e.g.,
calling it on each chunk of an iterative read operation.
The implementation needs work though, and I'm not convinced
Thank you for your answers.
I rather do not file a new bug, since what I coded isn't really a bug.
The problem I (my colleagues) have today is very stupid:
We read .csv files with a lot of columns, of which most contain
date-time stamps, coded in DD/MM/ HH:MM.
This is not exotic, but the base
The problem causing the stray worker processes when the master fails to
open a server socket to listen to connections from workers is not
related to timeout in socketConnection(), because socketConnection()
will fail right away. It is caused by a bug in checking the setup
timeout (PR 17391).
I would recommend reading https://adv-r.hadley.nz/base-types.html and
https://adv-r.hadley.nz/s3.html. Understanding the distinction between
base types and S3 classes is very important to make this sort of
question precise, and in my experience, you'll find R easier to
understand if you carefully d
> Kurt Van Dijck
> on Tue, 26 Mar 2019 21:20:07 +0100 writes:
> On di, 26 mrt 2019 12:48:12 -0700, Michael Lawrence wrote:
>> Please file a bug on bugzilla so we can discuss this
>> further.
> All fine. I didn't find a way to create an account on
> bugs.r-project
13 matches
Mail list logo
