fix: remove unused import get_window_option_value - code hygiene#289
Conversation
The two call sites use the fully-qualified `get_window_option_value_for` helper, leaving the imported `get_window_option_value` unused and triggering an `unused_imports` warning on build.
get_window_option_valueget_window_option_value - code hygiene
|
Hey @tarikguney, thank you so much for this! Really appreciate you taking the time to notice that stale import and cleaning it up properly rather than just scrolling past it. You are absolutely right, both call sites were already using the fully qualified path I have gone ahead and merged this in.Thank you! |
|
Hey @tarikguney, thank you so much for this! Really appreciate you taking the time to notice that stale import and cleaning it up properly rather than just scrolling past it. You are absolutely right, both call sites were already using the fully qualified path I have gone ahead and merged this in. Welcome to the psmux contributor list and I hope to see more from you! |
|
Thanks @psmux! Happy to be here. |
Problem
When I was isntalling the latest the psmux with cargo using the command
cargo install --git github.com/psmux/psmux, I ran into the following warning:Summary
get_window_option_valuesymbol from theoptionsuse-declaration insrc/server/mod.rs:26.crate::server::options::get_window_option_value_for(...)via the fully-qualified path, so the imported name is never referenced and triggers anunused_importswarning on build:Test plan
cargo buildcompletes without theunused_importswarning