Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename tree_scalar_mul to tree_scale #1196

Open
carlosgmartin opened this issue Feb 15, 2025 · 5 comments · May be fixed by #1198 or #1223
Open

Rename tree_scalar_mul to tree_scale #1196

carlosgmartin opened this issue Feb 15, 2025 · 5 comments · May be fixed by #1198 or #1223

Comments

@carlosgmartin
Copy link
Contributor

Minor suggestion: For convenience, rename

which are more concise.

If adopted, this could be done as follows:

  1. Rename the current functions in the code.
  2. Add back the old names as aliases. Make them emit deprecation warnings.
  3. After a deprecation period, delete the old names.

I can submit a PR for this.

@aryanmahawar205
Copy link

hey @carlosgmartin can you have a look at my PR and help figuring out what's possibly going wrong?

@rdyro
Copy link
Collaborator

rdyro commented Feb 23, 2025

Hey @aryanmahawar205 thanks for the contribution! I followed up on your PR #1198

@shreyans413
Copy link
Contributor

Hey @rdyro, if this issue isn't closed can i work on it?

@rdyro
Copy link
Collaborator

rdyro commented Mar 6, 2025

The PR is in progress here: #1198 by @aryanmahawar205 but in case work have stalled, it'd be great if you could take a look!

shreyans413 added a commit to shreyans413/optax that referenced this issue Mar 6, 2025
shreyans413 added a commit to shreyans413/optax that referenced this issue Mar 6, 2025
shreyans413 added a commit to shreyans413/optax that referenced this issue Mar 6, 2025
@shreyans413
Copy link
Contributor

The PR is in progress here: #1198 by @aryanmahawar205 but in case work have stalled, it'd be great if you could take a look!

Thanks for pointing this out! Since the previous PR (#1198) seemed inactive, I have submitted a new PR (#1223 ) to ensure progress on this. Let me know if any further changes are needed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment