Does variable lazy evaluation affect rule output when definitions appear after usage?

Variable Scope and Evaluation Order

In Less, variables are lazily evaluated, meaning their values are resolved at the point of use rather than at the point of declaration. This behavior allows a rule to reference a variable that is defined later in the same scope.

When a variable is declared multiple times within a single scope, the last definition typically takes precedence. This creates a scenario where the final compiled CSS may not align with the textual order of the source code, as subsequent declarations can retroactively change the values used in preceding rules.

Given this lazy loading mechanism, how does the compiler handle variable resolution when a variable is redefined after its initial use but before the end of the scope? Does this behavior persist across nested scopes, or does the resolution lock once the first rule is processed?