summary(warnings())
#> Length Class Mode
#> boolean operator not allowed for 'errors' objects, dropping errors 3 -none- call
#> boolean operator not allowed for 'errors' objects, dropping errors 3 -none- call
#> boolean operator not allowed for 'errors' objects, dropping errors 3 -none- call
#> boolean operator not allowed for 'errors' objects, dropping errors 3 -none- call
#> boolean operator not allowed for 'errors' objects, dropping errors 3 -none- call
#> boolean operator not allowed for 'errors' objects, dropping errors 3 -none- call
#> boolean operator not allowed for 'errors' objects, dropping errors 3 -none- call
#> boolean operator not allowed for 'errors' objects, dropping errors 3 -none- call
#> boolean operator not allowed for 'errors' objects, dropping errors 3 -none- call
#> boolean operator not allowed for 'errors' objects, dropping errors 3 -none- call
#> boolean operator not allowed for 'errors' objects, dropping errors 3 -none- call
#> boolean operator not allowed for 'errors' objects, dropping errors 3 -none- call
Also, this is ok for a scripting:
set_errors(1) + set_errors(2, 0.1)
but overkilling for an interactive session. Instead,
1 + set_errors(2, 0.1)
#> Warning message:
#> In Ops.errors(1, set_errors(2, 0.1)) :
#> first operand automatically coerced to an 'errors' object with zero error
is much more comfortable and one warning should suffice.
It's necessary to warn the user, but
generates 12 warnings:
Also, this is ok for a scripting:
but overkilling for an interactive session. Instead,
is much more comfortable and one warning should suffice.