Sandy Maguire
Sandy Maguire
It would be a _giant_ mess of CPP which IMO would only enhance the maintenance burden. We could alternatively remove the features from the existing plugin, but that seems like...
That's fair. I don't have strong opinions here; happy to acquiesce to whatever people think is best!
> What is the rationale for not wanting to port the full functionality? Complexity. Axing the metaprogramming component means we can remove: - the static plugin machinery that enables `[wingman||]`...
Your CI appears to be blocked by https://github.com/haskell/haskell-language-server/issues/2016
Wingman doesn't need to set it --- I never considered that someone would _intentionally_ turn off these warnings. We should enable the warning only if it wasn't explicitly set, but...
I think this should still be open --- we don't yet have "make **exports** explicit," do we?
Try enabling the `DEBUG` flag used by `Wingman.Debug` (I'm not sure how to enable it, sorry --- maybe just recompile with the debugging stuff in that module not commented out)....
- [x] **Haskell** by **isovector** (https://reasonablypolymorphic.com) : https://hackage.haskell.org/package/ldtk-types Haskell types and Aeson instances for parsing LDtk JSON files.
Usage: ```haskell data Tree = Leaf | Branch Tree Int Tree deriving (Data, Typeable) tree1 = Branch Leaf 0 $ Branch Leaf 1 $ Branch Leaf 2 Leaf tree2 =...
weird. what happens if there is no type annotation on `addP`? to be honest with you, these days I use this plugin exclusively to reload buffers in the repl :)