This will avoid some superfluous asJSON calls and possibly improve the coming "pre-validation" flow.
Desired behavior/Acceptance criteria (returned value, expected error, performance expectations, etc.)
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | ecarg | T383157 [25Q3] Improve performance and drive down tech debt & developer inhibitors | |||
| Resolved | cmassaro | T383573 Consider Returning `ZWrapper`s from builtin functions |
update (in case I forget): we will be doing this rather than another option (i.e. adding flags to builtin functions, etc)
It turns out that we can already do this: the extra ZWrapper.create after a builtin function runs would be a no-op if it received a ZWrapper. It would simply return the ZWrapper intact, including all internal state (which, ultimately, is what we want with this change: the ability to manipulate internal ZWrapper state from within builtin functions).
@cmassaro Could you please check if this is solved and "resolve" it if that is the case?