Using the or_fun_call lint will help maintainers to write functions that allow the program to evaluate lazily in the happy path. This should boost efficiency!
To enable the lint to run without warnings, I fixed one existing violation. Braces are added around the called to Pubkey::default(); otherwise, I ran into a clippy warning about a redundant closure. Let me know if there's an issue here.
Using the
or_fun_calllint will help maintainers to write functions that allow the program to evaluate lazily in the happy path. This should boost efficiency!To enable the lint to run without warnings, I fixed one existing violation. Braces are added around the called to Pubkey::default(); otherwise, I ran into a clippy warning about a redundant closure. Let me know if there's an issue here.