-
Notifications
You must be signed in to change notification settings - Fork 112
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
Link frontend contract tickets in the spec #1076
Conversation
Now that we have clearly identified the deltas between how the StableHLO dialect is used by frontends and what is specced (see https://github.com/orgs/openxla/projects/6), I figured it would be good to link these deltas in the spec, so that it's clear what areas are expected to change in the near future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM otherwise. |
Thank you for the thorough review! To address the comment about #606 and #714, indeed I haven't included them in the PR because I didn't find a great way to call them out. #606 is more of a double-check rather than something that I think will lead to change, and #714 is a particular case of the matter of associativity of reducers, so I figured it'd be fine to not mention them. |
Now that we have clearly identified the deltas between how the StableHLO dialect is used by frontends and what is specced (see https://github.com/orgs/openxla/projects/6), I figured it would be good to link these deltas in the spec, so that it's clear what areas are expected to change in the near future. As I was working on this pull request, I also called out several tickets which are not part of the Frontend Contract project, because they represented highly likely todos from the New Features project. I think this is also useful to include in the spec for the readers to understand the anticipated direction of StableHLO evolution.
Now that we have clearly identified the deltas between how the StableHLO dialect is used by frontends and what is specced (see https://github.com/orgs/openxla/projects/6), I figured it would be good to link these deltas in the spec, so that it's clear what areas are expected to change in the near future. As I was working on this pull request, I also called out several tickets which are not part of the Frontend Contract project, because they represented highly likely todos from the New Features project. I think this is also useful to include in the spec for the readers to understand the anticipated direction of StableHLO evolution.
Now that we have clearly identified the deltas between how the StableHLO dialect is used by frontends and what is specced (see https://github.com/orgs/openxla/projects/6), I figured it would be good to link these deltas in the spec, so that it's clear what areas are expected to change in the near future.
As I was working on this pull request, I also called out several tickets which are not part of the Frontend Contract project, because they represented highly likely todos from the New Features project. I think this is also useful to include in the spec for the readers to understand the anticipated direction of StableHLO evolution.