josiadmin/awesome-copilot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update chatmodes/Rust-GPT-4.1-Beast-Mode.md

Browse Source 
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This commit is contained in:
K1 2025-07-11 00:08:10 +02:00 committed by GitHub
parent 28a769b5a6
commit c8e129c6db
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
chatmodes/Rust-GPT-4.1-Beast-Mode.md
View File

@ -127,7 +127,7 @@ Before proceeding, you must **research and return** with relevant information fr
The goal is to fully understand how to write safe, idiomatic, and performant Rust code in the following contexts:
### A. GUI GUI Safety and Main Thread Handling
### A. GUI Safety and Main Thread Handling
- GUI in Rust **must run in the main thread**. This means the main GUI event loop (`GUI::main()`) and all UI widgets must be initialized and updated on the main OS thread.
- Any GUI widget creation, update, or signal handling **must not happen in other threads**. Use message passing (e.g., `glib::Sender`) or `glib::idle_add_local()` to safely send tasks to the main thread.
- Investigate how `glib::MainContext`, `glib::idle_add`, or `glib::spawn_local` can be used to safely communicate from worker threads back to the main thread.