Repository navigation
fix: reject MultiIndex constant operands under v1 - #1040
Merged
Merged
Conversation
Build cost — v1 vs legacyv1 build peak & time relative to legacy, on this commit — not a comparison against master (that is CodSpeed).
Full table (time + peak, mean)📊 Interactive plots + CSV: download the semantics-report-v1-vs-legacy artifact from this run. Report-only · not a gate · refreshed on every push · obsolete once legacy is dropped. |
Merging this PR will not alter performance
Comparing Footnotes
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related to #846.
Note
The following was generated by AI.
Changes proposed in this Pull Request
Under v1, arithmetic or comparison between a variable/expression and a constant
DataArrayon aMultiIndexdimension failed with an opaque xarray error, or silently produced an expression over theMultiIndex:broadcast_to_coords(the choke point for constant operands) now rejects, under v1, aMultiIndexdimension the target coords don't already carry. It raises the same message asadd_variables, with thereset_indexhint. This covers+ - * /, reflected ops,<= >= ==andadd_constraints.This is a step toward removing the
MultiIndexmachinery at 1.0 (#846).Checklist
AGENTS.md).doc.doc/release_notes.rstof the upcoming release is included.