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

Codify the meaning of "undefined" and "implementation-defined" #3775

Closed
handrews opened this issue May 2, 2024 · 3 comments
Closed

Codify the meaning of "undefined" and "implementation-defined" #3775

handrews opened this issue May 2, 2024 · 3 comments
Assignees
Labels
Milestone

Comments

@handrews
Copy link
Member

handrews commented May 2, 2024

We already use these terms a bit in the spec, but with PRs like these:

we are relying more on such descriptions to define areas of interoperability and expected compliance. A new subsection under the Definitions section seems like the best approach.

@handrews handrews added this to the v3.0.4 milestone May 2, 2024
@handrews handrews self-assigned this May 2, 2024
@handrews
Copy link
Member Author

handrews commented May 2, 2024

Thanks to @kevinswiber for suggesting this - Kevin (and anyone) please feel free to add suggestions or closely related terms that we should consider. I'll make a PR for this soon.

@miqui
Copy link
Contributor

miqui commented May 3, 2024

Thanks to @kevinswiber for suggesting this - Kevin (and anyone) please feel free to add suggestions or closely related terms that we should consider. I'll make a PR for this soon.

Agreed. Looking forward to the PR

@handrews
Copy link
Member Author

All PRs merged, closing!

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

No branches or pull requests

2 participants