-
-
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 19447 - [REG2.066] fixed size slice assignment in ctfe lose… #9071
Conversation
|
Thanks for your pull request, @WalterBright! Bugzilla references
|
|
It's a fairly serious bug, as it silently generates the wrong answer. |
2358490 to
8c87322
Compare
|
Please target stable. cc @UplinkCoder |
|
I don't think there's much point to targeting stable. This broke in version 2.066, and we're at 2.083 now. |
|
I'd remark that there is a bit of code duplication, |
It does mean LDC get the fixes sooner. |
|
Please add another test. |
|
@UplinkCoder why should that fail? |
8c87322 to
65bfeab
Compare
|
Why is there an extra commit "Merge branch 'stable' into fix19447" ? |
|
the code I posted changes an array at global scope; |
|
I'm putting this back into master, as it relies on some of the refactoring work I've done earlier. |
06ca8ce to
afc58e7
Compare
…s connection with array
afc58e7 to
c807c04
Compare
|
@UplinkCoder ok, but I had to rework it a bit, as the example is incomplete. |
Targeting stable however means GDC gets the fix later. :-) |
|
@ibuclaw not necessarily much later, as you can merge |
|
This PR has introduced a regression: https://issues.dlang.org/show_bug.cgi?id=20133 |
…s connection with array
The difficulty was that the interpreter failed to recognize a slice of a static array as being an lvalue.