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

Complain about RFC2119 terms, and fix usage #796

Merged
merged 2 commits into from
Dec 4, 2024

Conversation

inexorabletash
Copy link
Member

@inexorabletash inexorabletash commented Dec 3, 2024

A local change I had that needed dusting off. It's probably worth reviewing/merging, but not urgently.


Preview | Diff

@@ -1446,7 +1453,7 @@ dictionary MLTensorDescriptor : MLOperandDescriptor {

The {{MLTensor}} interface represents a tensor which may be used as an input or output to an {{MLGraph}}. The memory backing an {{MLTensor}} should be allocated in an [=implementation-defined=] fashion according to the requirements of the {{MLContext}} and the {{MLTensorDescriptor}} used to create it. Operations involving the {{MLTensor/[[data]]}} of an {{MLTensor}} occur on the {{MLContext/[[timeline]]}} of its associated {{MLContext}}.

Note: The [=implementation-defined=] requirements of how an {{MLTensor}} is allocated may include constraints such as that the memory is allocated with a particular byte alignment or in a particular memory pool.
The [=implementation-defined=] requirements of how an {{MLTensor}} is allocated may include constraints such as that the memory is allocated with a particular byte alignment or in a particular memory pool.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed this from an informative note to a normative statement since it seems to exactly be in the spirit of normative RFC2119's "may".

@inexorabletash
Copy link
Member Author

@huningxin & @fdwr - could you please review? But this is low priority!

@zolkis
Copy link
Collaborator

zolkis commented Dec 3, 2024

Looks good. Ugh. Spec editing is becoming super standardized. Almost programming. Might be good one day for automating implementations by AI. :)

Copy link
Collaborator

@fdwr fdwr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 q's and 1 typo, else LGTM.

index.bs Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
index.bs Show resolved Hide resolved
Copy link
Collaborator

@fdwr fdwr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Contributor

@huningxin huningxin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@huningxin huningxin merged commit df555e1 into webmachinelearning:main Dec 4, 2024
2 checks passed
github-actions bot added a commit that referenced this pull request Dec 4, 2024
SHA: df555e1
Reason: push, by huningxin

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@inexorabletash inexorabletash deleted the rfc2119 branch December 4, 2024 05:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants