Please let me know if I can be of any help. I kind of "caused" this issue
by submitting the new version of brms to CRAN.
Of course, the issue is not really in brms but somehow deeper as your
investigations shows. Would it help if brms
extracted variables names from rstan objects somehow differently
Yikes. Next question, is this (in your opinion) worth escalating to
r-devel ?
I can definitely implement something where I require() rstan up
front, (which should be harmless if it's really not available but will
fix issues that brms is having?) ... that might resolve the symptoms
cleanl
В Wed, 25 Sep 2024 12:28:25 -0400
Ben Bolker пишет:
>What is your current estimate of the probability that this is
> something that I've done wrong vs. exposing something wonky elsewhere
> (i.e. at the level of testthat, brms, rstan, Rcpp, R-devel, ...) ?
I didn't have a good answer (the m
On 9/25/24 12:21, Ivan Krylov wrote:
Hmm, so it's *not* a machine-specific problem after all [1,2] and can
now be reproduced on a regular R-devel build on Debian Sid. I'm sorry
for jumping to conclusions.
No need to apologize, you've gotten 1000x farther than I would have
on my own.
Hmm, so it's *not* a machine-specific problem after all [1,2] and can
now be reproduced on a regular R-devel build on Debian Sid. I'm sorry
for jumping to conclusions.
Why would Rcpp::loadModule() (called from rstan's .onLoad) end up trying
to apply a non-function, but only when being called from
