-
-
Notifications
You must be signed in to change notification settings - Fork 776
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
Document guidelines for when to use dynamically typed APIs #1127
Labels
enhancement
guide-new content
Additions; New content or section needed
needs: decision
Needs consensus decision from core devs
topic-c api
Comments
This was referenced Jun 26, 2023
erlend-aasland
changed the title
Document guidelines for strongly and weakly typed APIs
Document guidelines for when to use dynamically typed APIs
Jun 26, 2023
I suppose that a guideline should be decided in capi-workgroup/problems#31 first. |
Definitely! |
willingc
added
topic-c api
guide-new content
Additions; New content or section needed
needs: decision
Needs consensus decision from core devs
enhancement
and removed
enhancement
labels
Oct 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
guide-new content
Additions; New content or section needed
needs: decision
Needs consensus decision from core devs
topic-c api
We need to agree on guidelines for when to use and when to not use dynamically typed APIs.
See capi-workgroup/problems#31 (The C API is weakly typed)
In capi-workgroup/problems#31 (comment), @markshannon suggests:
The text was updated successfully, but these errors were encountered: