-
Notifications
You must be signed in to change notification settings - Fork 11
fixed max(), min(), range() for multiple inputs if one is non-finite #181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Thanks! Please add regresion tests |
Regression tests added and reverted to |
Is there anything more to do or can it be merged? |
#' Generating sequence of integer64 values | ||
#' | ||
#' @param from integer64 scalar (in order to dispatch the integer64 method of [seq()] | ||
#' @param from integer64 scalar (in order to dispatch the integer64 method of [seq()]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Run roxygenize()
for this to be cascaded to the man/ directory (or you can just edit it directly for this simple case)
I just need to find some time, hopefully this weekend. |
For #142
The example in issue #142 now works correctly.
I also fixed the behaviour that the warning is also shown in the case of range(NA_integer64_, na.rm=TRUE).
The same is applied to min.integer64 and max.integer64.