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

burner / test_migration2

0 stars 0 forks source link

D standard library not detected if I select "Release" as the current build configuration #45

Open burner opened 5 years ago

burner commented 5 years ago

x13989 reported this on 2019-05-31T09:21:23Z

Transfered from https://issues.dlang.org/show_bug.cgi?id=19927

CC List

r.sagitario

Description

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!

!!!There are attachements in the bugzilla issue that have not been copied over!!!

burner commented 5 years ago

r.sagitario commented on 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?

burner commented 5 years ago

x13989 commented on 2019-06-01T02:13:18Z

visualdproj

burner commented 5 years ago

x13989 commented on 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.

burner commented 5 years ago

x13989 commented on 2019-06-01T02:19:49Z

Disabling mixin analysis seems to work.

burner commented 5 years ago

x13989 commented on 2019-06-01T04:51:17Z

Is it possible to bring this problem a full fix?

burner commented 5 years ago

x13989 commented on 2019-06-01T06:23:44Z

I have attempted and disabling mixin analysis won’t help fixing this issue.

burner commented 5 years ago

x13989 commented on 2019-06-01T06:28:05Z

I found that Debug LDC works fine, but Release LDC is bugged as I described.

burner commented 5 years ago

x13989 commented on 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.

burner commented 5 years ago

x13989 commented on 2019-06-01T06:40:47Z

Created attachment 1749 Debug

burner commented 5 years ago

x13989 commented on 2019-06-01T06:41:45Z

Created attachment 1750 Debug

burner commented 5 years ago

x13989 commented on 2019-06-01T06:44:56Z

Created attachment 1751 Debug LDC

burner commented 5 years ago

x13989 commented on 2019-06-01T06:47:08Z

Created attachment 1752 Release

burner commented 5 years ago

x13989 commented on 2019-06-01T06:51:43Z

Created attachment 1753 Release LDC

burner commented 5 years ago

x13989 commented on 2019-06-01T06:52:17Z

Added some images to describe the bug

burner commented 4 years ago

r.sagitario commented on 2020-03-15T08:20:13Z

Does this also happen with the dmd based engine?