Logical inconsistency between class and method #1726
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For a first-time reader of R S3 system concepts, it goes without saying that
factor
is a method. It's actually the class. In the context of factors, for which the text is intended to explain sending theprint.factor
method, there are only two methods in question:1 -
print
which is the generic function to which we must entrust the sending of the appropriate method based, normally, on the class of the first argument;2 -
print.factor
which will be the appropriate method dispatched by the genericprint
function.Best regards.