> --
>
> Date: Wed, 17 Jan 2024 11:35:02 -0500
>
> From: Dipterix Wang
>
> To: Lionel Henry , Tomas Kalibera
>
>
>
> Cc: r-devel@r-project.org
>
> Subject: Re: [Rd] Choices to remove `srcref` (and its buddies) when
>
> serializing objects
>
> Message-ID: <3cf
Hi Travers,
This is an implementation detail for background workers in general, in that
there must be some robust way for them to exit (either upon a signal from the
main session, or if the main session ends / socket disconnects). As these are
background workers, their error messages are usuall
> Date: Wed, 15 Feb 2023 01:24:26 +0100
> From: Ben Engbers
> To: r-devel@r-project.org
> Subject: [Rd] Question on non-blocking socket
> Message-ID: <68ce63b0-7e91-6372-6926-59f3fcfff...@be-logical.nl>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> Hi,
>
> December 27, 2021 I
a patch at
> https://bugs.r-project.org/show_bug.cgi?id=17839
>
> In the meantime, you can use this stopgap implementation:
>
> https://github.com/tidyverse/purrr/blob/55c9a8ab8788d878ce9e8e80b867139e46d15395/src/conditions.c#L6
> L34
>
> Best,
> Lionel
>
> On 11/13/2
Perhaps my original question was too complicated, so I will just ask: is anyone
using R_GetCurrentEnv() in their C code? If so, grateful if you could point me
to an example where it is working for you.
I have searched Github and only come across a couple of trivial uses as an
argument to Rf_eva
Dear all,
I am attempting to use `R_GetCurrentEnv()` to return the current
environment within C code, but it seems to always return the global
environment.
Specifically, I would like to use it as an argument to R_NewEnv() so it
is created with the correct enclosing environment. I also have f
