-
-
Notifications
You must be signed in to change notification settings - Fork 606
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
fix Bugzilla 24745 - improve associative array syntax error message #16832
Conversation
Thanks for your pull request and interest in making D better, @royalpinto007! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please see CONTRIBUTING.md for more information. If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment. Bugzilla references
Testing this PR locallyIf you don't have a local development environment setup, you can use Digger to test this PR: dub run digger -- build "master + dmd#16832" |
6c67dd7
to
069ce3c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- I think the new message should only be shown when detecting a colon after a non-identifier expression. E.g. it looks like the message would show for
{expr expr}
, which is unlikely to be intended as an array initializer. - The message could say
(associative) array
, because array literals can have indexes too.
Edit: And (1) is why fail_compilation/fix350a.d and fail_compilation/fix350b.d are failing.
069ce3c
to
4074b14
Compare
ac9167c
to
3071bf1
Compare
3071bf1
to
16276df
Compare
Signed-off-by: royalpinto007 <royalpinto007@gmail.com>
16276df
to
d4b85e9
Compare
I think this can be merged as well? @thewilsonator |
no longer affect not assoc arrays
Enhance error messages for associative array syntax.