I used eCalc for a period a few years ago, tracing specific problems through the codebase as I hit them, and noted them down. I'm not currently working on eCalc, nor do I have concrete plans to do so. Still, since we now have Claude I thought it could sharpen my notes to the point where they're worth sending your way.
Some of these points are structural/architectural rather than isolated bugs, so they won't necessarily be quick to digest or resolve, and they don't all share the same audience on your end. Splitting them lets each be triaged, discussed, or closed independently instead of one thread trying to do everything. I have no expectation that any of this gets prioritized, and I'm fine with individual issues being closed as "not aligned with our direction."
Listed here as an index so there's one place that ties them together:
I used eCalc for a period a few years ago, tracing specific problems through the codebase as I hit them, and noted them down. I'm not currently working on eCalc, nor do I have concrete plans to do so. Still, since we now have Claude I thought it could sharpen my notes to the point where they're worth sending your way.
Some of these points are structural/architectural rather than isolated bugs, so they won't necessarily be quick to digest or resolve, and they don't all share the same audience on your end. Splitting them lets each be triaged, discussed, or closed independently instead of one thread trying to do everything. I have no expectation that any of this gets prioritized, and I'm fine with individual issues being closed as "not aligned with our direction."
Listed here as an index so there's one place that ties them together:
ConsumerFunctionextension point #1699