-
-
Notifications
You must be signed in to change notification settings - Fork 610
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 Issue 19661 - DMD 2.084.0 SIGSEGV in std.traits.isFunction #9652
Conversation
|
Thanks for your pull request and interest in making D better, @RazvanN7! 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 fetch digger
dub run digger -- build "master + dmd#9652" |
|
stable? |
|
Tried to, but I get conflicts. |
No error message is not good at all. Also this is not like a void init, the test case is more like immutable bool b = test();
void test(){}which outputs the impl. conv error I managed to get in the previous fix attempt. |
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.
void initialization != initialization with an expression of type void
|
@Geod24 @Basile-z I updated the patch. Now if any expressions are evaluated to |
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 see a small progress compared to my fix, i.e the line numbers, so this is good to my eyes
|
ping @Geod24 |
|
The |
Fixing the regression for this code led to outputting the error message : "Error: cannot implicitly convert expression of type void to immutable(bool)" ; the line number is missing, but it refers to line 3.
I wanted to fix that also by adding the line number to the error, but noticed that this code compiles fine:
In light of this example, I modified the code so that when an ExpInitializer that is evaluated to a VoidExpression is encountered, a VoidInitializer is returned. This made the code in the original bug post compile successfully, which I believe is the right fix.