reducing the "scope" of new_sorted_actual_scores

[jacobvosmaer]

I have refactored the calculation of sorted_actual_scores in best_match_for_query(). The assignment sorted_actual_scores = new_sorted_actual_scores was occurring later than necessary, making it harder to see that the sole purpose of the variable new_sorted_actual_scores is as a temporary variable for the removal of duplicates.

Would you agree that this improves the readability of the code?

[alnesbit]

Thanks. You're right that the calculation of sorted_actual_scores could be better positioned, and I agree this improves readability. I will merge this patch after testing.

[alnesbit]

Manually applied, committed and merged. Thanks!