S3 check error

[ElianHugh]

Hi again!

I was wondering whether it was possible to bypass or force the value of the s3 check in S3.r?

{Typed} exports a function as_assertion_factory, which modifies and spits out an assertion function for use in type checking. However, sourcing a module with as_assertion_factory in it results in the error:
Error in is_S3(b[[1L]]) || is_S3(b[-1L]) : invalid 'x' type in 'x || y'.
This occurs no matter what the supplied function is to the as_assertion_factory function.

This had actually been working last year, so it seems like a regression with {typed} or {box}, but I haven't been able to pinpoint what change in {box} or {typed} caused this to occur :(

I've tried to do some sneaky workarounds, like running as_assertion_factory in the on load hook, but ideally I'd like to not touch the globalenv.

Thank you for your help!

[klmr]

Thanks, that’s a regression in ‘box’. Since it’s a breaking bug I’ll try to get a hotfix ready by later today!

[klmr]

OK, fixing that was actually trivial but reproducing the bug for a regression test took me embarrassingly long. And I noticed additional errors in the function’s behaviour that also required fixing.

[klmr]

To use the fixed version before it is submitted to CRAN, please install hotfix-203, e.g. using ‘pak’ via

pak::pkg_install('klmr/box@hotfix-203')

(Since v1.0.2. was sent to CRAN just a few days ago, the next CRAN submission will only be in a few weeks to avoid swamping the maintainers.)

[ElianHugh]

To use the fixed version before it is submitted to CRAN, please install hotfix-203, e.g. using ‘pak’ via

pak::pkg_install('klmr/box@hotfix-203')

(Since v1.0.2. was sent to CRAN just a few days ago, the next CRAN submission will only be in a few weeks to avoid swamping the maintainers.)

Great, thanks for the quick fix!