dagql elective purity no jutsu

[cursive crane]

ah so the idea is that you set Pure: true when you're making the internal call that has a key attached, it looks like your changes have the opposite so far

since it's an override

so an impure unixSocket API can basically re-exec itself with a key/accessor passed as an argument and pure: true instead

and then each of those pure calls will be cached independently, with their accessor now as part of the cache key

without caching the original call

can sync on it tomorrow if you want!

[burnt lark]

Yeah with pleasure for tomorrow, a bit lost on that ahah 🙏

[cursive crane]

I'm around, can sync whenever

[burnt lark]

anytime, can join team audio with pleasure