Skip to content
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

Clarify what savvy won't support #56

Open
yutannihilation opened this issue Jan 12, 2024 · 1 comment
Open

Clarify what savvy won't support #56

yutannihilation opened this issue Jan 12, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@yutannihilation
Copy link
Owner

yutannihilation commented Jan 12, 2024

Never:

  • data frame input (treat it as a simple list)
  • data frame output (return a list and use tibble())

Unlikely:

  • Custom error class. There's no handy API for creating and raising a custom error. R_errorcall() doesn't provide a way to set custom classes. Actually, rlang's C implementation says "Probably should be implemented at R level."
  • ALTREP
  • matrix. There are too many options. But, how to deal with matrix (or dim) should be documented
@yutannihilation yutannihilation added the documentation Improvements or additions to documentation label Jan 12, 2024
@yutannihilation
Copy link
Owner Author

  • Clarify that it's highly unsafe to convert protected types (e.g. Owned...Sexp and FunctionCallResult) to Sexp is highly unsafe because it loses protection, and it's the user's responsibility to protect it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant