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

Simplify X::TypeCheck::Assignment for containers #5114

Merged
merged 1 commit into from Nov 30, 2022

Conversation

michaelruigrok
Copy link
Contributor

For container assignment type errors, change the message from: "Type check failed in assignment to an element of ; expected but got ()" to
"Type check failed for an element of ; expected but got ()".

This removes possible confusion about assignment syntax. Possibly resolves #5110.

This tweaks #5112 to try resolve any lingering confusion for people unfamiliar with container type declarations in Raku.

For container assignment type errors, change the message from:
"Type check failed in assignment to an element of <symbol>; expected <type> but got <type> (<value>)"
to 
"Type check failed for an element of <symbol>; expected <type> but got <type> (<value>)".

This removes possible confusion about assignment syntax. Possibly resolves  rakudo#5110.
@lizmat lizmat merged commit 1e30b43 into rakudo:master Nov 30, 2022
@lizmat
Copy link
Contributor

lizmat commented Nov 30, 2022

Thanks!

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.

Clarity in type errors for List and Map variables
2 participants