Five state containers can copy fields from a previous session, but nothing calls it yet.
State containers gained a carry-over method for seeding from a previous instance; no code path invokes it in this build.
What's wrong with this entry?
Five internal state containers gained a method for copying selected fields from a previous instance. Nothing in this build calls it, so no behaviour follows from it yet.
- Several caches and holders lost their reset and clear methods: the transcript recorder holder, the file content cache, the memory entries cache, and the ultracode latch.
- Some module-level singletons became lazily built per-host holders, including the IDE cache, which now keeps whether the JetBrains plugin is installed inside a host-scoped container.
continueFrom
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
Process-wide caches are now scoped per host
Both mention state
-
v2.1.235
Per-session state replaces process-wide globals, and the render root takes explicit dependencies
Both mention state
-
v2.1.235
More file-scope variables replaced by accessor-backed containers
Both mention state