Skip to content

always panic on non nil receivers and arguments#369

Closed
gaissmai wants to merge 1 commit intomainfrom
devel
Closed

always panic on non nil receivers and arguments#369
gaissmai wants to merge 1 commit intomainfrom
devel

Conversation

@gaissmai
Copy link
Owner

Behavior Changes:
Many table methods and serializers now assume non-nil receivers and will panic if called on nil, removing prior silent no-ops.

Tests:
Tests updated to assert panics for nil-receiver behavior across cloning, unions, equality/overlap checks, serialization/print/dump, and range-iteration helpers; auxiliary-table setups simplified.

Behavior Changes:
Many table methods and serializers now assume non-nil receivers and will
panic if called on nil, removing prior silent no-ops.

Tests:
Tests updated to assert panics for nil-receiver behavior across cloning,
unions, equality/overlap checks, serialization/print/dump, and range-iteration
helpers; auxiliary-table setups simplified.
@gaissmai
Copy link
Owner Author

@copilot review this PR

@gaissmai gaissmai closed this Feb 22, 2026
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