Solves base::rbind() issue when method is a list

[gerkovink]

CHANGED added unlist() to the return in check.method().

Illustration of the problem
When method is a list, e.g.

meth <- make.method(mammalsleep)
meth <- as.list(meth)

this will generally have no different behaviour from method being a vector as meth[i] would yield the same result either way. However, when the system is computationally singular, the loggedEvents will be updated. Then, in that process, when base::rbind() is called it returns an error from the unexported match.names() function if method is a list.

[stefvanbuuren]

OK, as a user convenience, and unlist cannot hurt. Even though it appears to work, we should not go any further and actually supporting the method argument as a list. Another route would be to actually intercept it.

[gerkovink]

Agreed and hence avoided in check.method(). No need for interception IMO as the help for the method argument specifically details use of either a single string or a vector of strings.