move collections to the end

I could see an argument for the collection being moved to the front as well. But I think either is a better case than in the middle.

I chose the end here because I think it reads easier when testing to have the function, then small decision making structs, _then_ the collection that could be constructed in place.

coverage_point_calculator/src/hexes.rs

@@ -25,8 +25,8 @@ pub struct CoveredHex {
 
 pub(crate) fn clean_covered_hexes(
     radio_type: RadioType,
-    ranked_coverage: Vec<RankedCoverage>,
     boosted_hex_status: BoostedHexStatus,
+    ranked_coverage: Vec<RankedCoverage>,
 ) -> Result<Vec<CoveredHex>> {
     // verify all hexes can obtain a base coverage point
     let covered_hexes = ranked_coverage
@@ -116,8 +116,8 @@ mod tests {
 
         let covered_hexes = clean_covered_hexes(
             RadioType::IndoorWifi,
-            vec![unboosted_coverage, boosted_coverage],
             boost_status,
+            vec![unboosted_coverage, boosted_coverage],
         )
         .unwrap();
 

coverage_point_calculator/src/lib.rs

@@ -141,7 +141,7 @@ impl CoveragePoints {
             BoostedHexStatus::new(&radio_type, location_trust_multiplier, &radio_threshold);
 
         let covered_hexes =
-            hexes::clean_covered_hexes(radio_type, ranked_coverage, boost_eligibility)?;
+            hexes::clean_covered_hexes(radio_type, boost_eligibility, ranked_coverage)?;
         let hex_coverage_points = hexes::calculated_coverage_points(&covered_hexes);
 
         let speedtests = speedtest::clean_speedtests(speedtests);