Skip to content

Conversation

@ricardoV94
Copy link
Member

*Remove structured_prefix for Ops that map 0->0
*Do not introduce new structured ops that don't map 0->0 besides the ones that already existed

Closes #1795

*Remove `structured_prefix` for Ops that map 0->0
*Do not introduce new structured ops that don't map 0->0 besides the ones that already existed
Copy link
Member

@jessegrabowski jessegrabowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving because of the first half, but why also remove the new functions? It's a strict upgrade. I only implemented for functions that map 0->0

@ricardoV94
Copy link
Member Author

I was convinced I removed only those that don't respect that. May have made a mistake...

@ricardoV94
Copy link
Member Author

import numpy as np

for op in ("exp2", "log2", "log10", "cos", "cosh", "arccos", "arccosh"):
    assert getattr(np, op)(0.0) != 0, op

Did I miss something?

@jessegrabowski
Copy link
Member

No, I didn't check closely enough. Carry on.

@ricardoV94 ricardoV94 merged commit 409a4b2 into pymc-devs:main Dec 21, 2025
64 checks passed
@ricardoV94 ricardoV94 deleted the sparse_name_change branch December 21, 2025 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

sparse math functions renamed accidentally

2 participants