Michel Lang
> In BatchJobs, I think argument resources (named list) of submitJobs() was the only way to pass a variable to the template, which then is also named resources. Is this...
A more general question: What is the intended behaviour if `x` or `y` have duplicated values? I'm a bit confused by the comment ``` # now this is checkSetEqual(..., ordered...
Also, `x != y` will not work with missing values. Edit: Well, at least not in all cases, e.g. `any(c(FALSE,NA) != c(FALSE, NA))`
Sorting comes after the length check, so this fails? ```r x = c(1, NA) y = c(1) ```
Ok, got it now. I think you could clarify a bit in the documentation, but otherwise good to be merged.
Sounds good to me.
Main problem is the variable lookup. If you can live with a little less informative error messages, the quickest way to do the assertions is with `qassertr`: ```r qassertr(list(paperwidth, paperheight),...
Just wondering: Do you encounter this often? It is not hard to write something like an apply for assertions, e.g.: ```r aapply = function(fun, formula, ...) { fun = match.fun(fun)...
I have interest in including such a function in the package. Regarding varying parameters for checks, what do you think of using the vector recycling of `mapply`? ```r aapply =...
I basically agree with @tdeenes: if the assertion is of general use and helpful for a broad range of applications, then checkmate is the right place for the assertion. Maybe...