similar to: Inquiry about the behaviour of subsetting and names in matrices

Thank you for such a quick reply, here are some points that I think might have been missed: > I would state the question the other way : why are NAs integer indices allowed? > In my experience, they are sometimes useful but they often delay the detection of bugs. However, due to backward compatibility, this feature cannot be removed. Adding this feature to character indices would worsen the

Karolis wrote: > Hello, > I have stumbled upon a few cases where the behaviour of naming and subsetting in matrices seems unintuitive. > All those look related so wanted to put everything in one message. > 1. Why row/col selection by names with NAs is not allowed? > x <- setNames(1:10, letters[1:10]) > X <- matrix(x, nrow=2, dimnames = list(letters[1:2],

But this might require a more detailed investigation. For example I just noticed that even with the patch `@` is still not listed in .S3_methods_table(). KK. > On Apr 29, 2023, at 4:44 PM, Karolis Koncevi?ius <karolis.koncevicius at gmail.com> wrote: > > Hello Kurt, > > With r84341 it now works on my side. > > Warm regards, > Karolis K. > >> On Apr 29,

>>>>> Karolis Koncevi?ius writes: > But this might require a more detailed investigation. For example I > just noticed that even with the patch `@` is still not listed in > .S3_methods_table(). Afaict base does not register any methods for @ or @<- ? -k > KK. >> On Apr 29, 2023, at 4:44 PM, Karolis Koncevi?ius <karolis.koncevicius at gmail.com> wrote:

Hello Kurt, With r84341 it now works on my side. Warm regards, Karolis K. > On Apr 29, 2023, at 1:24 PM, Kurt Hornik <Kurt.Hornik at wu.ac.at> wrote: > >>>>>> Karolis Koncevi?ius writes: > > Can you pls try again with r84341 or later? > > Best > -k > >> A more concrete example in order to correct my vague messages below. >> Writing

>>>>> Karolis Koncevi?ius writes: Can you pls try again with r84341 or later? Best -k > A more concrete example in order to correct my vague messages below. > Writing an R package that uses `@` and `@<-` as S3 generics. Line from manual pages in .Rd files: > \method{@}{newclass}(object, name) <- value > Throws this error during R CMD check ?as-cran >

A more concrete example in order to correct my vague messages below. Writing an R package that uses `@` and `@<-` as S3 generics. Line from manual pages in .Rd files: \method{@}{newclass}(object, name) <- value Throws this error during R CMD check ?as-cran Bad \usage lines found in documentation object ?code?: <unescaped bksl>method{@}{newclass}(object, name) <-

Thank you for such a quick reply, Gabriel, I am not too familiar with the package tools, so cannot speak too confidently, but below is how I see the issue currently. The issue is not for external packages to rely on unexported functions from tools::, rather the issue is that 'R CMD check ?as-cran' runs those functions from tools:: in order to check the validity of Rd files (from any

Karolis, It seems likely, without having looked myself, that you could be correct about the issue, but it does seem worth noting that both of the functions you have mentioned are not exported, and thus not part of the API that extension packages are allowed to use and rely on. If retrieving the list of "internal S3 generics" is something package and user code is allowed to do, the real

This issue might go deeper - I was not successful in passing R CMD checks for the usage files. R CMD check kept showing errors for `@` declarations, even thou they were identical to `$` declarations (which passed fine). Seems like the usage check functions are not prepared for `@` - also in tools:::.S3_method_markup_regexp > On Apr 28, 2023, at 10:34 PM, Karolis Koncevi?ius

I agree, this is a good idea and would be very helpful in interactive contexts. I have a draft patch implementing this feature here: https://github.com/r-devel/r-svn/pull/122 (Append ?.patch? to the URL to get a raw patch.) Regards, Tomasz > On Mar 31, 2023, at 2:11 PM, Karolis K <karolis.koncevicius at gmail.com> wrote: > > Hello, > > In the current R-devel @ is S3

>>>>> Karolis Koncevi?ius >>>>> on Mon, 9 Dec 2019 23:43:36 +0200 writes: > So I tried adding Infinity support for all cases. > And it is (as could be expected) more complicated than I thought. "Of course !" Thank you, Karolis, in any case! > It is easy to add Inf support for the test. The problems start with conf.int=TRUE.

Thank you for a fast response. Nice to see this mailing list being so alive. Regarding Inf issue: I agree with your assessment that Inf should not be removed. The code gave me an impression that Inf values were intentionally removed (since is.finite() was used everywhere, except for paired case). I will try to adjust my patch according to your feedback. One more thing: it seems like you

Hello, In the current R-devel @ is S3 generic, so we can do things like - for example - use it to extract matrix rows by name: .S3method("@", "mm", function(object, name) object[name,]) m <- structure(matrix(rnorm(20), ncol=2), dimnames=list(paste0("row", 1:10), paste("col", 1:2)), class="mm") m at row1 However, seems like

I was building a package that uses the new generic @ and kept having errors with ?roxygen2? documentation. ?roxygen2? generated NAMESPACE added `@.newclass` as a newly exported function, not as a S3method. At first I thought this must be a bug in roxygen2 and they lag behind the new developments in R. But after some investigation I found that ?roxygen2? is using tools:::.get_internal_S3_generis()

Hello, Writing to share some things I've found about wilcox.test() that seem a a bit inconsistent. 1. Inf values are not removed if paired=TRUE # returns different results (Inf is removed): wilcox.test(c(1,2,3,4), c(0,9,8,7)) wilcox.test(c(1,2,3,4), c(0,9,8,Inf)) # returns the same result (Inf is left as value with highest rank): wilcox.test(c(1,2,3,4), c(0,9,8,7), paired=TRUE)

We're using Dovecot v1.2.15 LDA/IMAP/POP3+MySQL with quota plugin, quota_rule per-user size, quota_exceed_message and quota_warning on storage=90%%.with script. Everything is working as expected. But I've been asked to configure it the way, that when a user gets message, which would make his maildir over quota limit, notification go not only to sender, but also to postmaster at domain.com.

In specific cases fligner.test() can produce a small p-value even when both groups have constant variance. Here is an illustration: fligner.test(c(1,1,2,2), c("a","a","b","b")) # p-value = NA But: fligner.test(c(1,1,1,2,2,2), c("a","a","a","b","b","b")) # p-value < 2.2e-16

Dead R developers, In R-devel 2023-02-11 and older R versions, there is a note in the "lm {stats}" help page specifying that: > Offsets specified by offset will not be included in predictions by predict.lm<http://127.0.0.1:12534/library/stats/help/predict.lm>, whereas those specified by an offset term in the formula will be. However, the source code as well as basic tests

Dear R-Helpers, I am working on a dataset containing ca. 500 specimens of 17 different species. The data is three text columns, followed by ca 70 columns of binary data. I'm trying to write a function that will allow me to interactively exclude species using the inofrmation in the third text column. My function, matrix.slicer, appears to work as I intend. However, when I pass the