(Sorry for only getting back to this more than a month later.) В Mon, 8 Apr 2024 17:03:00 +0000 Jorgen Harmse <jhar...@roku.com> пишет:
> What is the policy for changing something that is wrong? There is a > trade-off between breaking old code that worked around a problem and > breaking new code written by people who make reasonable assumptions. First of all, quantify the breakage. Does the proposed change break `make check-devel`? Does it break CRAN and BioConductor? (This one is hard to measure properly: someone will have to run >20000 R CMD checks times two, for "before the change" and "after the change".) Given a persuasive case, breaking changes can still be made, but will require a deprecation period to let the packages adjust. If you would like to try your hand at developing a patch and make a case for it at R-devel or the Bugzilla, the resources at <https://contributor.r-project.org/> can be helpful. -- Best regards, Ivan ______________________________________________ R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
