← Back to index | Original Bugzilla link

Bug 19927 – D standard library not detected if I select "Release" as the current build configuration

Status
NEW
Severity
major
Priority
P2
Component
visuald
Product
D
Version
D2
Platform
All
OS
Windows
Creation time
2019-05-31T09:21:23Z
Last change time
2023-10-18T20:22:17Z
Assigned to
No Owner
Creator
Srxy Wang
Moved to GitHub: visuald#251 →

Attachments

IDFilenameSummaryContent-TypeSize
1749Screen Shot 2019-06-01 at 2.26.25 PM.pngDebugimage/png439595
1750Screen Shot 2019-06-01 at 2.26.25 PM.pngDebugimage/png439595
1751Screen Shot 2019-06-01 at 2.26.32 PM.pngDebug LDCimage/png439635
1752Screen Shot 2019-06-01 at 2.28.07 PM.pngReleaseimage/png437862
1753Screen Shot 2019-06-01 at 2.28.07 PM.pngRelease LDCimage/png437862

Comments

Comment #0 by x13989 — 2019-05-31T09:21:23Z
D Win32 project, VD 0.49.2, VS 16.1.1. If I select the Debug or Release (either x86 or x64) build configuration, everything works properly. But if I switch the build configuration to Debug LDC/Release LDC, the auto-completion and go-to-definition function of the standard library won't work. It would say "No definition found for 'writeln'", and there are nothing but keywords in the completion list. These issues would no longer occur if I switch back to Debug/Release. I suspect that Visual D's not identifying LDC's standard library files lead to this problem. Please fix this!
Comment #1 by r.sagitario — 2019-05-31T17:14:20Z
When trying to reproduce this, it doesn't seem to fail in general, but switching between LDC and DMD seems to freeze the semantic engine by some mixin handling. The issue goes away if I disable "mixin analysis". Is this the case for you, too? BTW: what project type do you use, visualdproj or vcxproj?
Comment #2 by x13989 — 2019-06-01T02:13:18Z
visualdproj
Comment #3 by x13989 — 2019-06-01T02:17:02Z
I don’t know why the stdlib gets undetected when I switch the build config to LDC. I’ve tried to add ldc\bin to Path, but it doesn’t helps.
Comment #4 by x13989 — 2019-06-01T02:19:49Z
Disabling mixin analysis seems to work.
Comment #5 by x13989 — 2019-06-01T04:51:17Z
Is it possible to bring this problem a full fix?
Comment #6 by x13989 — 2019-06-01T06:23:44Z
I have attempted and disabling mixin analysis won’t help fixing this issue.
Comment #7 by x13989 — 2019-06-01T06:28:05Z
I found that Debug LDC works fine, but Release LDC is bugged as I described.
Comment #8 by x13989 — 2019-06-01T06:33:27Z
Sorry, I’ve described the condition wrongly. It should be: The problem only occurs in Release/Release LDC, and doesn’t occurs under Debug/Debug LDC. It isn’t related with LDC, I’m sorry for my wrong description before.
Comment #9 by x13989 — 2019-06-01T06:40:47Z
Created attachment 1749 Debug
Comment #10 by x13989 — 2019-06-01T06:41:45Z
Created attachment 1750 Debug
Comment #11 by x13989 — 2019-06-01T06:44:56Z
Created attachment 1751 Debug LDC
Comment #12 by x13989 — 2019-06-01T06:47:08Z
Created attachment 1752 Release
Comment #13 by x13989 — 2019-06-01T06:51:43Z
Created attachment 1753 Release LDC
Comment #14 by x13989 — 2019-06-01T06:52:17Z
Added some images to describe the bug
Comment #15 by r.sagitario — 2020-03-15T08:20:13Z
Does this also happen with the dmd based engine?
Comment #16 by robert.schadek — 2023-10-18T20:22:17Z
THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/visuald/issues/251 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB