feat: support type aliases and includes in IDL

[m62624]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @m62624, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the IDL system by introducing support for type aliases and a robust file inclusion mechanism. These features improve the modularity and reusability of IDL definitions, enabling developers to define custom type shortcuts and organize their IDL files more effectively. The changes are integrated across the IDL parser, metadata generation, and client generation components, ensuring comprehensive support and correct behavior for these new capabilities.

Highlights

• IDL Type Alias Support: The IDL now supports defining type aliases (e.g., alias MyType = u32;), which are correctly parsed, represented in the Abstract Syntax Tree (AST), and used by the client generator to produce corresponding Rust pub type declarations.
• IDL Include Mechanism: A new preprocessing step has been introduced to support !@include: directives within IDL files, allowing for modular IDL definitions and recursive inclusion of other IDL files.
• Duplicate Include Prevention: The IDL preprocessor ensures that each included file is processed only once, preventing redundant definitions and potential infinite loops in recursive includes.
• Type Hashing Consistency: Alias types are now hashed identically to their target types, ensuring consistent type identification and metadata generation across the system.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces support for type aliases and !@include directives in the IDL, which is a great feature enhancement. The changes are comprehensive, touching the parser, AST, client generator, and templates to accommodate these new features. A new preprocessor is also added to handle the include logic. The implementation is solid, but I've identified a bug in the client code generator that results in a trailing comma in generic type parameter lists. I've also noted a potential robustness issue in the preprocessor's logic for detecting top-level scope, which could be improved for future maintainability. Overall, great work on this feature.