Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.269,
Internal ChangesSection of the release
What
The check that rejects a new asynchronous REPL (code execution) request when too many evaluations are already queued or running, along with its "async REPL dispatch rejected" message, was moved into a new internal function that is now invoked through the call.runEngine execution path. The wording and the logic itself are unchanged.
Why
This is a code relocation tied to the broader REPL tool restructuring in this release, with no change in behavior: the same queue-depth limit still applies.
