Sebastian Meyer

> 1. `R CMD build` succeeds but the child Rmd file is missing in `inst/doc` I'd put child documents in a *subdirectory* such as `vignettes/inputs/` (to avoid misinterpretation as main...

Great to see this issue has already been reported in such detail. Just today I failed to reproduce results from a simulation study run with future.apply 1.8.1 + future 1.21.0...

I guess the following comment from the sources of the **methods** package also holds for "xts": https://github.com/wch/r-source/blob/be05889aa5646e2c456486fd584be873ef3acd62/src/library/methods/R/BasicClasses.R#L531-L532 So maybe **xts** itself could `setOldClass("xts")` ?

Ok, I see. Maybe the check could be done earlier and more efficiently? Something like https://github.com/bastistician/mboost/commit/50a03928f6d884bbd3a73c2115b1f26a4d3f00ce ? Of course, being an mboost noob, I have no idea whether checking the...

I have not been able to reproduce this, but it seems many here are seeing that strange NULL warning. It would be interesting to understand where this is coming from....

@markvanderloo, what's your current view on this wish? I'm considering a "soft" transition from (now way too heavy for my taste) **testthat** to **tinytest**. It would be nice to be...

I see. A setup file which could do anything doesn't really fit into the design of **tintest**. It is indeed attractive to view test scripts as independent R code that...

To clarify, I see this issue more as a wishlist item than a bug in **knitr**. A simpler solution for `error=TRUE` chunks might be to comment the code in the...

> I am just worried that a lot of potential users will bail after seeing that it over-writes `

Thanks for the clarifications. I agree that **inops** should not hack around the default message about masking `