Closed jeanetteclark closed 5 years ago
ifelse
requires quite a bit of care to use in package code that takes user input as it isn't type stable and does funny things seemingly more often than not. See https://vctrs.r-lib.org/articles/stability.html#ifelse. So this change is 💯 .
When testing on a system that had the error described in issue #278 , this change makes the error go away and the code runs as expected. Still not sure of the root cause of the issue - some setups don't like
ifelse
for some reason - but this removes the offending function at least