On Fri, Mar 3, 2017 at 9:55 AM, Hadley Wickham <h.wick...@gmail.com> wrote:
>> But, how you propose a warning-to-error transition should be made
>> without wreaking havoc? Just flip the switch in R-devel and see CRAN
>> and Bioconductor packages break overnight? Particularly Bioconductor
>> devel might become non-functional (since at times it requires
>> R-devel). For my own code / packages, I would be able to handle such
>> a change, but I'm completely out of control if one of the package I'm
>> depending on does not provide a quick fix (with the only option to
>> remove package tests for those dependencies).
>
> Generally, a package can not be on CRAN if it has any warnings, so I
> don't think this change would have any impact on CRAN packages. Isn't
> this also true for bioconductor?
Having a tests/warn.R file with:
warning("boom")
passes through R CMD check --as-cran unnoticed. Same with:
if (sample(2) == 1) message("It's your lucky day today!")
/Henrik
PS. Does testthat signal that?
>
> Hadley
>
> --
> http://hadley.nz
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
