> On 24 Sep 2026, at 3:27 PM, Eric Auger <[email protected]> wrote: > > v9 has changed the way new field values are stored. writable field props > and non writable field props could have different setters. A non > writable field setter just needs to check the new value is the same as > the current host value. No need to record the new value in the hashtable > for further commitment.
How will that work? as based on certain vCPU init options, non-writable fields will change… right? Warm Regards, Khushit
