Re: [R-pkg-devel] UX for "WARNING unable to translate to native encoding"?

2021-08-16 Thread David Norris
Thanks to you both, Ivan and Tomas. Capital D it is, then. -David From: Tomas Kalibera Date: Monday, August 16, 2021 at 8:48 AM To: Ivan Krylov , David Norris Cc: "r-package-devel@r-project.org" Subject: Re: [R-pkg-devel] UX for "WARNING unable to translate to native encoding

[R-pkg-devel] UX for "WARNING unable to translate to native encoding"?

2021-08-16 Thread David Norris
Whereas Unicode U+00d7 (times), U+00b1 (plus-minus) and U+03bc (mu) have equivalents in Latin-1 encoding, and I have used these without difficulty in strings, neither U+2206 (INCREMENT) nor U+0394 (Greek Delta) does: https://en.wikipedia.org/wiki/ISO/IEC_8859-1 Consequently, my attempt to use a p

Re: [R-pkg-devel] Using parallel:::sendMaster &c. despite warnings

2021-07-23 Thread David Norris
   cheers     Ben Bolker On 7/23/21 1:17 PM, David Norris wrote: My understanding about this issue with progressr is that it is nontrivial, and will take author Henrik Bengtsson some time & thought to resolve. OTOH if patches to 'parallel' were welcome, I could embed my sol

Re: [R-pkg-devel] Using parallel:::sendMaster &c. despite warnings

2021-07-23 Thread David Norris
new parameters (e.g., mc.prog=NULL) to support progress reporting consistently with the existing interface. From: Duncan Murdoch Date: Friday, July 23, 2021 at 11:26 AM To: Hugh Parsonage , David Norris Cc: "r-package-devel@r-project.org" Subject: Re: [R-pkg-devel] Using parallel:

Re: [R-pkg-devel] Using parallel:::sendMaster &c. despite warnings

2021-07-23 Thread David Norris
on: Friedrich-Alexander-Universität Erlangen-Nürnberg (FAU) Date: Friday, July 23, 2021 at 8:05 AM To: David Norris , "r-package-devel@r-project.org" Subject: Re: [R-pkg-devel] Using parallel:::sendMaster &c. despite warnings Am 23.07.21 um 13:19 schrieb David Norris: Because paral

[R-pkg-devel] Using parallel:::sendMaster &c. despite warnings

2021-07-23 Thread David Norris
is warning an absolute deal-killer on CRAN? Is there a 'correct' way to do `:::` that avoids the warning altogether? Kind regards, David Norris __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] Best way to build CRAN packages that include Rust source?

2021-06-23 Thread David Norris
.com/dcnorris/precautionary/tree/main/src The GitHub workflow is at https://github.com/dcnorris/precautionary/blob/main/.github/workflows/R-CMD-check.yaml Kind regards, David From: R-package-devel on behalf of David Norris Date: Monday, May 3, 2021 at 2:44 PM To: "r-package-devel@r-project.org&

[R-pkg-devel] Best way to build CRAN packages that include Rust source?

2021-05-03 Thread David Norris
I am appreciating 2 distinct approaches currently used to compile Rust code in R packages: 1. LinkingTo: cargo, as done in https://CRAN.R-project.org/package=salso 2. A more ‘traditional’-looking approach built on Autoconf & Automake https://CRAN.R-project.org/package=gifski Is there any reaso

Re: [R-pkg-devel] Win-builder not finding binaries provided by LinkingTo: cargo?

2021-04-07 Thread David Norris
out for the community. OTOH, crucial calculations in ‘precautionary’ parallelize so nicely with mclapply() that it would not be inappropriate to bypass (forkless) Win by setting OS_type to unix. From: Kevin Ushey Date: Tuesday, April 6, 2021 at 6:41 PM To: David Norris Cc: "r-package-de

[R-pkg-devel] Win-builder not finding binaries provided by LinkingTo: cargo?

2021-04-06 Thread David Norris
For version 0.2-2 of my ‘precautionary’ package, I have added fast numerical routines implemented in Rust. In my DESCRIPTION file, I am “LinkingTo: cargo (>= 0.1.28)”, but fail incoming check on Win-builder as follows: https://win-builder.r-project.org/incoming_pretest/precautionary_0.2-2_2021040