Pandiyan

Thanks for the clarification and for taking the time to review this. It sounds like the current behavior may be intentional due to underlying constraints. If that’s the case, I...

Thanks for the detailed explanation @ *MacroBull* My goal with the docs change was only to clarify the user-facing requirement and error message; the deeper hashing design decisions make sense...

@sfc-gh-lwilby Thanks for the suggestion! That makes sense. I’ll update the documentation to explain the rerun model, content-based hashing via __reduce__(), and why non-pickleable objects (like functions) can cause errors...

Docs: clarify picklable requirement for st.cache_resource Clarifies that st.cache_resource requires pickle-able objects in addition to being hashable, aligning the documentation with current caching behavior and addressing confusion reported in #1399....

Thanks for the clarification that makes sense, and I agree this is more precise. You're right that pickle-ability is only required for the fallback hashing path, not as a strict...