-
Notifications
You must be signed in to change notification settings - Fork 20.6k
Document "invocation correctness" development principle #2320
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
Labels
Comments
That seems like a good place. |
So boo plain objects, right? |
I started a wiki page that we can use to iterate, it might be a little easier to do there than on a PR. Or maybe harder, I dunno, but you can just start editing with your ideas if you want. People don't generally read any of this, so usually it will be us linking to it to justify not changing (or changing) some reported behavior. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Ref #2134 (comment)
We now (modulo particularly hairy backwards compatibility issues) consider it safe to assume that all function input matches a documented signature, and therefore allow functions to throw exceptions rather than fail silently. This should be captured somewhere, and my first thought was CONTRIBUTING.md.
The text was updated successfully, but these errors were encountered: