Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Specify -fobject-code when launching intero
See original GitHub issueHi @rikvdkleij
One optimisation that Intero for Emacs uses is to set -fobject-code when launching intero so that only those modules that have changed are recompiled; this scales well for large projects. With the default -fbyte-code all modules are reloaded every time with :load.
(:reload will load just the recent module, but switching modules causes a big reload of everything. So that’s a trade-off)
Setting -fdefer-type-errors helps get more type info be available, at the cost of slightly slower compile due to GHC.
Just wanted to add that in case it wasn’t known.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Done in beta45, https://github.com/rikvdkleij/intellij-haskell/releases/tag/v1.0.0-beta45. Also uploaded to the JB plugin repo but can take some days before they have approved.
Created alternative solution for
:browse! *moduleNameby using the parser and type info.REPL switches to byte-code when info is requested.
It’s possible to temporarily
:set -fbyte-codeand:reloadto get information for the current module then:set -fobject-codeback afterward. Intero does that if it uses:infoand doesn’t get anything back. It’s definitely a matter of figuring out what works for you at this point.