Fix issue 18586 - improve error message for disabled generated opAssign - #23818
Merged
thewilsonator merged 1 commit intoSep 9, 2026
Merged
Conversation
When a struct's generated opAssign is disabled because a field's own opAssign is disabled, checkDisabled() previously reported the generic 'generated function ... cannot be used because it is annotated with @disable' message, without pointing to the actual field responsible. This mirrors the existing handling for disabled generated postblit (bugzilla issue 21885) by walking the struct's fields and reporting the first field whose opAssign is disabled, e.g.: Error: struct `S` is not assignable because field `f` is not assignable Updated test/fail_compilation/disable.d to match the new message.
thewilsonator
approved these changes
Sep 9, 2026
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
2 participants
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.
Fixes #18586