Skip to content

Move enums from typing -> enums - #2037

Closed
mdboom wants to merge 1 commit into
NVIDIA:mainfrom
mdboom:move-enums
Closed

Move enums from typing -> enums#2037
mdboom wants to merge 1 commit into
NVIDIA:mainfrom
mdboom:move-enums

Conversation

@mdboom

Copy link
Copy Markdown
Contributor

As discussed offline, we could instead put all our enums into their own module, rather than in typing.

@mdboommdboom added P0 High priority - Must do! cuda.core Everything related to the cuda.core module breaking Breaking changes are introduced labels May 6, 2026
@mdboommdboom self-assigned this May 6, 2026
@leofang

Copy link
Copy Markdown
Member

I don't like it 🥲

@leofang

Copy link
Copy Markdown
Member

I prefer cuda.core.typing for all-in-one dumpster, including enums.

By the original design this is a non-issue. Instead of allowing passing cuda.core.enum.AddressingMode.HMM we would have limited to only passing "HMM" (a str), and then we would have added cuda.core.typing.AddressingModeType = Literal["HMM", "ATS"]. So by this argument they belong to typing too, not enum. Enum is IMHO an artificial construct and implementation detail.

@github-actions

Copy link
Copy Markdown

@mdboommdboom closed this May 6, 2026
github-actionsBot pushed a commit that referenced this pull request May 7, 2026
Removed preview folders for the following PRs:
- PR #1910
- PR #2018
- PR #2031
- PR #2035
- PR #2037
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breakingBreaking changes are introducedcuda.coreEverything related to the cuda.core moduleP0High priority - Must do!

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@mdboom@leofang