call to stack / get-cabal-configuration delays editing file

[bergey]

call to stack / get-cabal-configuration delays editing file

[sergv]

@bergey Thanks for bringing this up. Unfortunately I'm not actively maintaining nor actually using flycheck-haskell any more, however I can merge some small fixes. Your patch sounds great and is probably what should ultimately be done.

However, for me issue with merging your proposed patch that makes the calls asynchronous is that once something breaks, someone will have to debug and fix it. Would you be interested in maintaining this part of flycheck-haskell going forward once it's merged?

Regarding your questions about async dependency and output from get-cabal-configuration:

• I think async is ok since choosing something different will likely result in some kind of dependency. Although perhaps emacs threads need to be considered
• I think it's resonable to where get-cabal-configuration will print its output. The assumption is reasonable and the file is under our control anyway

[bergey]

Yes, I'd be happy to maintain this part of flycheck-haskell going forward. I've been using my patch for several weeks now; I'll try to turn it into a PR sometime in the next week.