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

chore: Move codegen to separate crate #1467

Merged
merged 1 commit into from
Aug 25, 2023

Conversation

tottoto
Copy link
Collaborator

@tottoto tottoto commented Aug 20, 2023

Motivation

Compilation fails before code generation in bootstrap tests if there is no code to include during development. Or, by the other any reason, when compilation fails because of the generated code, there are same cases as well. In these case, it is necessary to temporarily disable include in the code by commenting out, etc., run bootstrap test, and then re-enable include again, which feels troublesome.

Separating code generation into a independent crate solves this problem. In addition, since it is possible to check that the generated code is updated with a simple command, the program can be easier by separating it from the code generation process.

Solution

Adds a codegen crate, which is responsible for code generation, and moves out the change detection in generated code to the external process.

@tottoto tottoto force-pushed the move-codegen-to-separate-crate branch from aacf071 to d3a732a Compare August 20, 2023 14:35
@LucioFranco LucioFranco added this pull request to the merge queue Aug 25, 2023
Merged via the queue into hyperium:master with commit 44aa46d Aug 25, 2023
16 checks passed
@tottoto tottoto deleted the move-codegen-to-separate-crate branch August 26, 2023 01:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants