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

[0029] Cooperative Vectors: consider using unique interpretation enums for variable vs memory #402

Open
damyanp opened this issue Feb 21, 2025 · 0 comments · May be fixed by #409
Open

[0029] Cooperative Vectors: consider using unique interpretation enums for variable vs memory #402

damyanp opened this issue Feb 21, 2025 · 0 comments · May be fixed by #409
Assignees
Labels
active proposal Issues relating to active proposals

Comments

@damyanp
Copy link
Member

damyanp commented Feb 21, 2025

#398 (comment)

There are two types of interpretations in the spec currently:

  1. Interpreting vectors stored in variables
  2. Interpreting vectors / matrices store in memory

These both use the same enum. This means that there are values in the enum that don't apply to the memory resources (ie the packed ones) that we'll need to do work to prohibit using.

If we used a different enum for these then we woudn't have this problem. Having an additional enum might be confusing / annoying to work with though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
active proposal Issues relating to active proposals
Projects
Status: No status
Status: Triaged
Development

Successfully merging a pull request may close this issue.

1 participant