Skip to content
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

Jump to bottom

Analysis not keeping up with refactoring #19080

Closed
stevemessick opened this issue May 29, 2014 · 5 comments
Closed

Analysis not keeping up with refactoring #19080

stevemessick opened this issue May 29, 2014 · 5 comments
Assignees
@bwilkerson
Labels
area-analyzer Use area-analyzer for Dart analyzer issues, including the analysis server and code completion. closed-not-planned Closed as we don't intend to take action on the reported issue
Milestone
1.8

Comments

@stevemessick
Copy link
Contributor

While refactoring call-site from method A to method B, I need to reanalyze sources between every small change to make search results of function calls to A up-to-date. If I don't calls already changed to B will show up in the results for searches of calls to A.
////////////////////////////////////////////////////////////////////////////////////
Editor: 1.4.0.dev_06_06 (2014-05-13)
OS: Windows 7 - amd64 (6.1)
JVM: 1.7.0_01

projects: 6

open dart files: 13

auto-run pub: true
localhost resolves to: 127.0.0.1
mem max/total/free: 1791 / 1791 / 1284 MB
thread count: 42
index: 297700 relationships in 71506 keys in 278 sources

SDK installed: true
Dartium installed: true

Attachment:
screenshot.png (225.04 KB)
@scheglov
Copy link
Contributor

I don't see how this issue is related to refactoring.
Not analyzing is not a refactoring problem.

Removed the owner.
Removed Area-Editor label.
Added Area-Analyzer label.

@kasperl
Copy link

kasperl commented Jul 10, 2014

Removed this from the 1.6 milestone.
Added Oldschool-Milestone-1.6 label.

@kasperl
Copy link

kasperl commented Aug 4, 2014

Removed Oldschool-Milestone-1.6 label.

@bwilkerson
Copy link
Member

The problem is the performance of the analyzer, which is always a concern, but this issue does not specify any specific criteria by which we can know whether or not we are done.

Set owner to @bwilkerson.
Added NotPlanned label.

@clayberg
Copy link

Added this to the 1.8 milestone.

@stevemessick stevemessick added Type-Defect area-analyzer Use area-analyzer for Dart analyzer issues, including the analysis server and code completion. closed-not-planned Closed as we don't intend to take action on the reported issue labels Nov 28, 2014
@stevemessick stevemessick added this to the 1.8 milestone Nov 28, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bwilkerson bwilkerson

Labels
area-analyzer Use area-analyzer for Dart analyzer issues, including the analysis server and code completion. closed-not-planned Closed as we don't intend to take action on the reported issue
Projects
None yet
Milestone
1.8
Development

No branches or pull requests
5 participants
@scheglov @kasperl @bwilkerson @stevemessick @clayberg