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

Warn that in future arguments after the initial (prediction, ground_truth) positional arguments will become keyword-only in optax losses. #863

Merged
merged 1 commit into from
Mar 19, 2024

Conversation

copybara-service[bot]
Copy link

@copybara-service copybara-service bot commented Mar 12, 2024

Warn that in future arguments after the initial (prediction, ground_truth) positional arguments will become keyword-only in optax losses.

This is to prevent users from accidentally passing in the wrong order of arguments, and to make interfaces functionally more similar (e.g. after partialling loss-specific hyper-parameters).

@copybara-service copybara-service bot changed the title Make arguments after the initial (prediction, ground_truth) positional arguments, keyword-only arguments in optax losses. Arguments after the initial (prediction, ground_truth) positional arguments should be keyword-only in optax losses. Mar 12, 2024
@copybara-service copybara-service bot force-pushed the test_615023064 branch 5 times, most recently from 7095640 to 919ad6b Compare March 13, 2024 15:47
@copybara-service copybara-service bot changed the title Arguments after the initial (prediction, ground_truth) positional arguments should be keyword-only in optax losses. Warn that in future arguments after the initial (prediction, ground_truth) positional arguments will become keyword-only in optax losses. Mar 13, 2024
@copybara-service copybara-service bot force-pushed the test_615023064 branch 3 times, most recently from adff4d4 to 6a2911d Compare March 19, 2024 12:18
…ruth) positional arguments will become keyword-only in optax losses.

This is to prevent users from accidentally passing in the wrong order of arguments, and to make interfaces functionally more similar (e.g. after partialling loss-specific hyper-parameters).

PiperOrigin-RevId: 617138212
@copybara-service copybara-service bot merged commit ca9c109 into main Mar 19, 2024
@copybara-service copybara-service bot deleted the test_615023064 branch March 19, 2024 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant