Skip to content

Improve the save operation of DartEditor #2895

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

Closed
DartBot opened this issue May 4, 2012 · 2 comments
Closed

Improve the save operation of DartEditor #2895

DartBot opened this issue May 4, 2012 · 2 comments
Labels
closed-duplicate Closed in favor of an existing report

Comments

@DartBot
Copy link

DartBot commented May 4, 2012

This issue was originally filed by @tomyeh


As the application getting bigger, the save operation of DartEditor is coming unacceptable - from tens seconds to a couple of minutes! To be productive, I was forced to use other text editor and invoke frogc manually.

I know it is tough and the Dart team must work on JDT-like incremental compilation. However, before the performance issue is really solved, I suggest to introduce an option that allows the user to turn off the compilation for each save. Then, the user can invoke the compilation at any proper moment he prefers.

@anders-sandholm
Copy link
Contributor

AFAIK, we're looking at both speeding up things as well as making the operation asynchronous.


Added Area-Editor, Triaged labels.

@danrubel
Copy link

We are in the process of making analysis more performant.
You can try it out by following the instructions here...
http://code.google.com/p/dart/issues/detail?id=2297


Added Duplicate label.
Marked as being merged into #2297.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-duplicate Closed in favor of an existing report
Projects
None yet
Development

No branches or pull requests

3 participants