From b3ec478de982803c5522206d1c646fb6c80edeb8 Mon Sep 17 00:00:00 2001
From: rudy <rudy.sicard@gmail.com>
Date: Mon, 22 May 2023 16:49:22 +0200
Subject: [PATCH] fix(optimizer): optimize partition in reverse order

note: it was initially the case, but it was simplified and we didn't see shortcomings on tests.
---
 .../src/optimization/dag/multi_parameters/optimize.rs           | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/compilers/concrete-optimizer/concrete-optimizer/src/optimization/dag/multi_parameters/optimize.rs b/compilers/concrete-optimizer/concrete-optimizer/src/optimization/dag/multi_parameters/optimize.rs
index 2fdc4a5b5..3cb4bff34 100644
--- a/compilers/concrete-optimizer/concrete-optimizer/src/optimization/dag/multi_parameters/optimize.rs
+++ b/compilers/concrete-optimizer/concrete-optimizer/src/optimization/dag/multi_parameters/optimize.rs
@@ -861,7 +861,7 @@ pub fn optimize(
 
     let mut fix_point = params.clone();
     for iter in 0..=10 {
-        for partition in 0..nb_partitions {
+        for partition in (0..nb_partitions).rev() {
             let new_params = optimize_macro(
                 security_level,
                 ciphertext_modulus_log,