[tlively]

When evaluating top-level statements in evalCtor, local values were previously serialized directly into localExprs. If getSerialization failed (e.g. because it tried to serialize a continuation), localExprs lost the serialized local state from the last successfully evaluated statement. This could leave previously initialized non-nullable locals uninitialized in the partially evaluated function. It could also cause evalCtor to spuriously emit local.sets overwriting parameters with default values.

Serialize locals into a temporary nextLocalExprs vector and only move it into localExprs once all locals have been serialized.

[gemini-code-assist]

Code Review

This pull request updates src/tools/wasm-ctor-eval.cpp to serialize local expressions into a temporary vector first, only updating localExprs once all locals succeed. This prevents partial serialization failures from corrupting the previous state. The changes are accompanied by new test cases in test/lit/ctor-eval/cont-noserial.wast. The review feedback suggests a performance improvement to reserve capacity for the temporary vector upfront to avoid dynamic reallocations.