it is not clear why did you choose to expose the embarrassing option
rather then detecting compiler crash and restarting it automatically?
since compiler does crash all the time, and there is no resolution is sight,
can you please improve the embarrassment? :-)
1) provide preference settings to enable compiler auto restart
with some kind of limit/throttle per same file, so auto restart will cease for "really bad files"
2) provide simple square colored "compiler control" ui widget which would:
thank you
Eclipse -> Scala -> Restart Presentation Compiler
rather then detecting compiler crash and restarting it automatically?
since compiler does crash all the time, and there is no resolution is sight,
can you please improve the embarrassment? :-)
1) provide preference settings to enable compiler auto restart
with some kind of limit/throttle per same file, so auto restart will cease for "really bad files"
2) provide simple square colored "compiler control" ui widget which would:
- show if compiler running/crashed status with green/orange color
- allow restart compiler with 1 click, not 5 as it is now (when clicked on the widget)
thank you
Leave a comment
on 2015-01-25 21:06 *
By Simon Schäfer
What do you mean by compiler crashes all the time? What are the errors you get and are they solved after a restart? Do they reappear after some time?
on 2015-02-20 18:55 *
By Andrei Pozolotin
1) crashes all the time == the more complex file is the more frequent the crashes are
i.e. introduction of quasi-quotes, path dependent types, increases crash probability 10 fold
2) errors are == typical false positives: missing imports, missing type members
3) yes, errors are resolved by restart. restart can be done in one of few ways:
a) restart eclipse
b) close/open file
c) CTRL-SHIFT-F reformat the file
4) yes, same types of errors appear in same places after some work on other, independent types in the file.
i.e. introduction of quasi-quotes, path dependent types, increases crash probability 10 fold
2) errors are == typical false positives: missing imports, missing type members
3) yes, errors are resolved by restart. restart can be done in one of few ways:
a) restart eclipse
b) close/open file
c) CTRL-SHIFT-F reformat the file
4) yes, same types of errors appear in same places after some work on other, independent types in the file.
No file chosen
You have an empty file field. Please select or remove it.
Name | Size |
---|