D issues are now tracked on GitHub. This Bugzilla instance remains as a read-only archive.
Issue 17260 - Pending semantic analysis request
Summary: Pending semantic analysis request
Status: RESOLVED FIXED
Alias: None
Product: D
Classification: Unclassified
Component: visuald (show other issues)
Version: D2
Hardware: x86_64 Windows
: P1 enhancement
Assignee: No Owner
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-16 05:22 UTC by Heromyth
Modified: 2017-06-05 16:49 UTC (History)
1 user (show)

See Also:


Attachments
Error (212.45 KB, image/png)
2017-03-16 05:22 UTC, Heromyth
Details
Error snap (207.84 KB, image/png)
2017-03-16 05:23 UTC, Heromyth
Details
It's ok for some projects. (211.66 KB, image/png)
2017-03-16 05:29 UTC, Heromyth
Details

Note You need to log in before you can comment on or make changes to this issue.
Description Heromyth 2017-03-16 05:22:01 UTC
Created attachment 1640 [details]
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 Heromyth 2017-03-16 05:23:40 UTC
Created attachment 1641 [details]
Error snap

It's ok for some projects.
Comment 2 Heromyth 2017-03-16 05:27:32 UTC
Comment on attachment 1641 [details]
Error snap

Sorry, this image is obsolete
Comment 3 Heromyth 2017-03-16 05:29:38 UTC
Created attachment 1642 [details]
It's ok for some projects.
Comment 4 Rainer Schuetze 2017-03-17 08:39:28 UTC
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 Rainer Schuetze 2017-03-17 08:59:28 UTC
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 Heromyth 2017-03-18 01:27:15 UTC
(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 Heromyth 2017-03-18 02:12:19 UTC
(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 Rainer Schuetze 2017-06-05 16:49:14 UTC
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.