-
Notifications
You must be signed in to change notification settings - Fork 46
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
Move some existing enums into block 0x0001 #420
Comments
[1] I'm not really sure whether [ |
Aren't they native-specific though? As in they wouldn't be exposed in the Web ever? |
My note [1] is specifically about |
Dec 12 meeting:
|
Writing out all of the current extension structs to make sure I know what block they belong in:
|
Dec 19 meeting:
|
Kinda sorta blocked on #490. If we decide to just merge block 1 into block 0 it will be a lot easier because I won't have to rework the generator to allow multiple block numbers in one file, which it currently can't do. |
This has been scrapped, because in #490 we're merging block 1 into block 0. Block 1 won't exist anymore. |
For #214, we need to move some things into block 0x0001. Filing separately because I forgot about it when it was part of that issue.
Not sure how the codegen will work for this, but see #417 for a first attempt.
The text was updated successfully, but these errors were encountered: