chore: remove deno runtime

[xusd320]

This pull request removes the crates/runtime crate from the workspace and deletes all of its code and configuration files. The main impact is a simplification of the project structure by eliminating an unused or deprecated runtime component.

Project structure cleanup:

• Removed the crates/runtime crate from the workspace by deleting its entry from the exclude list in the root Cargo.toml and deleting its directory. [1] [2]
• Deleted all source code in crates/runtime/src/lib.rs, including the bootstrap function and related imports, as well as the test module.
• Removed the crates/runtime/Cargo.toml configuration file, eliminating all dependency and package metadata for the runtime crate.

[gemini-code-assist]

Summary of Changes

Hello @xusd320, 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 focuses on streamlining the project by completely removing the crates/runtime component. This action simplifies the workspace configuration and eliminates associated source code and build metadata, contributing to a cleaner and more manageable codebase.

Highlights

• Workspace Configuration Update: The crates/runtime entry has been removed from the exclude list in the root Cargo.toml file, signifying its complete removal from the project workspace.
• Runtime Crate Deletion: The entire crates/runtime crate, including its Cargo.toml and src/lib.rs files, has been deleted, eliminating all associated code and configuration.
• Project Simplification: This pull request simplifies the overall project structure by removing an apparently unused or deprecated Deno runtime component.

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 correctly removes the crates/runtime crate, which was based on the Deno runtime. The changes are straightforward, involving the deletion of the crate's directory and updating the root Cargo.toml to reflect this removal. This is a good cleanup that simplifies the project structure by removing an unused component. I've reviewed the changes and found no issues.