-
Notifications
You must be signed in to change notification settings - Fork 87
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
Use hdevtools for error checking #47
Comments
In the meantime, I use this Build system:
Update: Made it parse warnings You can jump through the errors with Sublime's inbuilt |
There are hdevtools.py module with |
If you pass However, we have to watch out that like in ghci, the warnings will only be shown once (at the first successful compile), and then only as soon as you change something in the file (doing that and re-checking is super fast in hdevtools though). |
Also relevant: bitc/hdevtools#18 (Using multiple files with same htdevtools instance) |
What kind of cache do you mean there? hdevtools doesn't make any special caches, the only benefit is that it doesn't initialize&configure ghc every time. |
I just mean the information that is loaded into memory - probably the same as would be loaded in a ghci session:
It would be nice if you could load both modules at the same time, getting the speed benefit hdevtools gives you across multiple modules. |
will reload "Module1" or just add "Module2". |
@mvoidex I implemented your suggestion for hdevtools and ghc-mod. This allows us to type check whole projects really fast. |
Closing this issue. Assuming it was implemented. |
We don't actually use hdevtools's speed with
hdevtools check
yet, do we?The text was updated successfully, but these errors were encountered: