This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 17
Rewriting linter-javac in ES(6?) #76
Labels
Milestone
Comments
Proof the implementation of performance tests. |
This was referenced Feb 18, 2016
This was referenced Feb 18, 2016
Closed
Closed
I recently put performance metrics into |
Great idea - thanks @Arcanemagus. I guess i'll implement something similar. |
Is this project abandoned or forgotten about? Nothing has progressed for 4 years. |
No. I don't use Atom anymore and i don't program Java currently. So i felt no pressure about it. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am currently working hard making bugs testable, ironing bumps out and enhance the use of classpaths in general.
It unfortunately seems to be a huge effort to make the linter-javac-plugin 🚬-testable without touching the plugin itself. I currently don't want to add any untested functionality to prevent delivering a failure to our users.
Therefore i file this issue to collect ideas and feedback on the rewrite which will be accomplished with the "Release 2.0.0"-Milestone.
🎅 Wish List
Every wish will become a separate issue, to allow us the detailed discussion of concerns.
sourcepath
-option for speedup (see Linter javac painfully slow #98). 🐎en
withUTF-8
encoding by using-J-Duser.language=en
and-J-Dfile.encoding=UTF-8
(see Does not lint #36).atom-javaenv
-package to use its API to the Java-Environment. 🌟 🔧 🌟-sourcepath
to improve compilation speed #99). 💅Help me
The text was updated successfully, but these errors were encountered: