Bug 17260 – Pending semantic analysis request

Status
RESOLVED
Resolution
FIXED
Severity
enhancement
Priority
P1
Component
visuald
Product
D
Version
D2
Platform
x86_64
OS
Windows
Creation time
2017-03-16T05:22:00Z
Last change time
2017-06-05T16:49:14Z
Assigned to
nobody
Creator
bitworld

Attachments

IDFilenameSummaryContent-TypeSize
1640error.pngErrorimage/png217544
1641error.pngError snapimage/png212830
1642ok.pngIt's ok for some projects.image/png216737

Comments

Comment #0 by bitworld — 2017-03-16T05:22:01Z
Created attachment 1640 Error My development environment is: VisualD-v0.44.1 DMD v2.073.2 Windows 10 x64 Visual Studio 2015 I have a project, see https://github.com/Heromyth/Iup4D. The code completion does not always work when I edit the source code in my solution. Please check the attachment. Everything is OK for VisualD-v0.44.0-beta2.
Comment #1 by bitworld — 2017-03-16T05:23:40Z
Created attachment 1641 Error snap It's ok for some projects.
Comment #2 by bitworld — 2017-03-16T05:27:32Z
Comment on attachment 1641 Error snap Sorry, this image is obsolete
Comment #3 by bitworld — 2017-03-16T05:29:38Z
Created attachment 1642 It's ok for some projects.
Comment #4 by r.sagitario — 2017-03-17T08:39:28Z
I don't think this is a regression from 0.44-b2, nothing has chnaged in the semantic engine. Instead, it very much depends on where you trigger the completion box and what imports are in that file. You are hitting an endless loop when the semantic engine tries to evaluate std.algorithm.setops.cartesianProduct for UFCS expansion. You might want to disable UFCS expansions in the Intellisense options as it will also improve the speed of the completion box.
Comment #5 by r.sagitario — 2017-03-17T08:59:28Z
This version doesn't fix the failing analysis, but cancels it with the next analysis request: https://ci.appveyor.com/project/rainers/visuald/build/job/fw9w1e6mq6h3dg9n/artifacts
Comment #6 by bitworld — 2017-03-18T01:27:15Z
(In reply to Rainer Schuetze from comment #4) > I don't think this is a regression from 0.44-b2, nothing has chnaged in the > semantic engine. Instead, it very much depends on where you trigger the > completion box and what imports are in that file. > You are right. This problem is also there for VisualD-0.44-b2. It didn't happen so often during I used it.
Comment #7 by bitworld — 2017-03-18T02:12:19Z
(In reply to Rainer Schuetze from comment #5) > This version doesn't fix the failing analysis, but cancels it with the next > analysis request: > https://ci.appveyor.com/project/rainers/visuald/build/job/fw9w1e6mq6h3dg9n/ > artifacts Now, the pending message just shown for a while, and disappeared. However, the completion box wasn't there. I have pushed my latest code to the repository for the test. In onCreated() in module iup.color, I can get the box when I input "this." . In onCreated() in module iup.menu, I failed to get the box when I input "this.". All the projects can be built successfully.
Comment #8 by r.sagitario — 2017-06-05T16:49:14Z
Completion on the respective code should work with https://github.com/dlang/visuald/releases/tag/v0.45.0-beta1 Enabling UFCS might yield too many entries, though.