-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugs 17918, 18143, 18145 - debugcall() issues #2
Comments
As I'm responsible for that I'm happy to collaborate on a fix in either direction (i.e., with me working in collab with R-core, or me mentoring/overseeing work by others in prep for submission to R-core). I will be on hand for Sessions 1 and 3 |
I have started working on fixes to at least some of these issues and will continue |
I have filed (one part) of the |
I've filed the narrower, separable warning bug here: https://bugs.r-project.org/show_bug.cgi?id=18370 with a patch |
@gmbecker: Thank you for your inputs on these issues. I'll have a look later this week. |
I've submitted a patch for https://bugs.r-project.org/show_bug.cgi?id=18145 which also fixes https://bugs.r-project.org/show_bug.cgi?id=18143 in the process. |
https://bugs.r-project.org/show_bug.cgi?id=17918
func
simply by evaluatingcall[[1L]]
inparent.frame(2L)
?methods::isGeneric(funsym)
call, which actually seems to be one option to fix Bug 18143 (another one is to use thefdef
argument ofisGeneric()
).func <- getS3method(genname, class(arg))
, which does not reliably find the S3 method that will eventually be called. Furthermore,class(arg)
is bad asgetS3method()
expects a single class name.These related issues are best worked on in one go.
The text was updated successfully, but these errors were encountered: