-
Notifications
You must be signed in to change notification settings - Fork 213
rewrite: Module output and base architecture #867
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
base: master
Are you sure you want to change the base?
Conversation
6b0735d to
054ed82
Compare
|
This looks very promising. |
|
Sure, the next step in my mind would be to actually implement struct/union generation. For that we need lifetime propagation. I think it would be convenient to be able to discuss this in some kind of group chat for ash development. I'd usually use Discord for this, but I'm open to suggestions as I'm not adamant on it. |
|
@Friz64 there is a gitter instance for this repository. Link should be in the readme, it's using the old repo url because gitter couldn't migrate. You can use various clients like Matrix to connect. |
13a80c2 to
7808fe6
Compare
754e26b to
6dae1b3
Compare
|
I've gone ahead and touched up this PR from the ground up. The module structure is now extensions at the top level just like current ash, Vulkan feature levels at |
This is based on #745 and eddyb's C parsing PR (Friz64#1). This PR will be rebased once these are merged.
I only implemented the most basic of struct outputs to have something to work with, extending that is the next step.