Failed Assert error message in comptime can display call stack out of order

[jfecher]

Aim

Writing code with a failing assert at comptime, several functions deep.

Expected Behavior

The resulting error message should show the call stack in order.

Note that in the following example, or_else should not assert(self._is_some);:

error: Assertion failed
    ┌─ std/option.nr:33:16
    │
 33 │         assert(self._is_some);
    │                -------------
    │
    ┌─ std/meta/expr.nr:235:22
    │    
235 │             let result = result.or_else(|| modify_block(self, f));
    │                          ----------------------------------------
    ·    
244 │             let result = result.or_else(|| modify_let(self, f));
    │                          --------------------------------------
    ·    
340 │   ╭     expr.as_block().map(
341 │   │         |exprs: [Expr]| {
342 │   │         let exprs = modify_expressions(exprs, f);
    │   │                     ----------------------------
343 │   │         new_block(exprs)
344 │   │     }
345 │   │     )
    │   ╰─────'
    ·   │
449 │ ╭       expr.as_let().map(
450 │ │           |expr: (Expr, Option<UnresolvedType>, Expr)| {
451 │ │           let (pattern, typ, expr) = expr;
452 │ │           let pattern = pattern.modify(f);
453 │ │           let expr = expr.modify(f);
454 │ │           new_let(pattern, typ, expr)
    │ │           ---------------------------
455 │ │       }
456 │ │       )
    │ ╰───────'
    · │  
540 │         exprs.map(|expr: Expr| expr.modify(f))
    │         --------------------------------------
    ·    
650 │             quote { let $pattern = $expr; }.as_expr().unwrap()
    │             --------------------------------------------------
    │    
    ┌─ src/main.nr:15:3
    │
 15 │ #[inject_context]
    │   --------------
    ·
 38 │     let body = f.body().modify(|expr| mapping_function(expr, f));
    │                -------------------------------------------------
    │

Bug

The call stack is instead grouped by the file and shown by the line order in the file rather than the call order.

To Reproduce

Workaround

None

Workaround Description

No response

Additional Context

No response

Project Impact

None

Blocker Context

No response

Nargo Version

No response

NoirJS Version

No response

Proving Backend Tooling & Version

No response

Would you like to submit a PR for this Issue?

None

Support Needs

No response