#S7 does just what I want, but dare I use it in anything that needs to be maintainable? OO R implementations get replaced so quickly. Is it better to just pretend the only options are #S3 and #S4? #rstats
I can't seem to create an #S7 object that inherits from base class array or matrix, so unless I'm being spectacularly stupid (always an option) S7 won't do the job anyway; my data structures are irretrievably 3d #rstats
@sjcowtan They are not replaced quickly, that's why there are so many. But S7 is < 1.0.0 so not quite production ready. There might be some breaking changes down the path.
@Lluis_Revilla That's a good reason not to use it yet, indeed. Thanks for the clarification.
@sjcowtan I think it should be more safe than not to use s7 given that it’s coming from the R consortium. https://github.com/RConsortium/S7/pull/400/files
Draft R dev blog post by t-kalinowski · Pull Request #400 · RConsortium/S7

Draft blog post for the R development blog, detailing the recent changes in base R which enabled S7 to be published to CRAN. (refocused iteration of #311)

GitHub
@sjcowtan ah, I take that back the point in another reply is more prescient.
@zkamvar @sjcowtan And S4 came from none other than John Chambers. Maybe OO in a functional language is a bad idea...