Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! 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 improves the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request introduces several improvements for co_await support in AUI, including enabling coroutines by default and enhancing AFuture to better handle void types and ensure thread consistency during coroutine resumption. However, a critical vulnerability was identified in the AFuture coroutine implementation: forcing resumption on the caller thread can lead to deadlocks and potential crashes on non-AUI managed threads. Additionally, there's a potential issue in the await_suspend implementation regarding mutable lambdas and a bug in JpgImageLoader::save where an incorrect parameter is passed to stbi_write_jpg_to_func (passing stride instead of a quality value). A minor performance improvement opportunity also exists in the AJsonConv specialization for AMap.
I have made some adjustments for AUI's
co_awaitsupport.Generally my experience was good enough to switch from callback-based async handling to
co_awaits.