feat: clarify error message for bounced types from which accessed a field that does not fit in 224 bytes #1111
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.
Previously, the following code would produce a confusing error:
Now, it gives following error:
If the type specifies only one field, it will look like this:
It's way too big, but since we don't have a more complex UI for errors (like in Rust), a long clear message with all the details is better than a short but not very clear message.
Issue
Closes #1021.
Checklist