Daniel Cousens

@ARkrOSClou sorry, I misunderstood the report/question and mistakenly moved this to a GitHub discussion. I'm unable to re-open the original issue.

@adaboese I find myself using the following pattern quite often ```typescript const zMyType = z.object({ something: z.string(), // this pattern json: z.string().transform((x, ctx) => { try { return JSON.parse(x) }...

lgtm, but internal server error... probably an upstream bug

@rich-harris @xtuc should we still be using this?

Hi @kursataktas, this seems pretty interesting! I might look into it for a few weeks, but generally we haven't added third party resources to our README or elsewhere.

> guarantee that the compiler didn't copy parts of that data to other places > (like the stack). @sipa can you ever make that guarantee? At least, not without checking...