⚡ Bolt: Optimize LanguageSelector lookups #104
Conversation
💡 What:
Replaced O(N) linear search in `LanguageSelector` with an O(1) Map lookup.
Added `supportedLanguagesMap` to `SupportedLanguages.kt` to cache the lookup map.
🎯 Why:
The `LanguageSelector` component was iterating over the full list of ~300 languages on every recomposition to find language names and filter recent languages. This caused unnecessary CPU work on the main thread during UI updates.
📊 Impact:
Reduces lookup complexity from O(N) to O(1).
Significantly faster rendering when the language list is large.
🔬 Measurement:
Verified by code inspection that `find { ... }` is replaced by `map[...]`.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
This change improves the performance of the
LanguageSelectorcomponent by replacing repeated linear searches over thesupportedLanguageslist with O(1) map lookups. It introduces asupportedLanguagesMapin the utility file which is computed once, and updates the UI component to use this map for resolving language names and filtering recent languages. This reduces the computational overhead during recompositions.PR created automatically by Jules for task 15103903178078622377 started by @menny