Cocoindex is an incremental framework . https://cocoindex.io/docs/programming_guide/core_concepts/ one of the key aspect is memoization. so you only reprocess what's needed
Right now
We have users ask - they may not want to memoize embedding calls for storage tradoffs.
Right now memoization is only supported at function level, but it may make more sense to decide at call site level.
For example sometimes user may not want to memoize for embedding always.
Open discussion - What's the relationship of define at
- function def level
- callsite level
what to decide on the final effect when defined at the two place.
鉂わ笍 Contributors, please refer to 馃摍Contributing Guide.
Unless the PR can be sent immediately (e.g. just a few lines of code), we recommend you to leave a comment on the issue like I'm working on it or Can I work on this issue? to avoid duplicating work. Our Discord server is always open and friendly.
Cocoindex is an incremental framework . https://cocoindex.io/docs/programming_guide/core_concepts/ one of the key aspect is memoization. so you only reprocess what's needed
Right now
These defined by user at function definition - https://cocoindex.io/docs/programming_guide/function/#change-detection-and-memoization
We have users ask - they may not want to memoize embedding calls for storage tradoffs.
Right now memoization is only supported at function level, but it may make more sense to decide at call site level.
For example sometimes user may not want to memoize for embedding always.
Open discussion - What's the relationship of define at
what to decide on the final effect when defined at the two place.
鉂わ笍 Contributors, please refer to 馃摍Contributing Guide.
Unless the PR can be sent immediately (e.g. just a few lines of code), we recommend you to leave a comment on the issue like
I'm working on itorCan I work on this issue?to avoid duplicating work. Our Discord server is always open and friendly.