Skip to content
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

backpack leaves cabal-docspec very confused #74

Open
ekmett opened this issue Feb 20, 2021 · 3 comments
Open

backpack leaves cabal-docspec very confused #74

ekmett opened this issue Feb 20, 2021 · 3 comments
Labels
help wanted Extra attention is needed

Comments

@ekmett
Copy link

ekmett commented Feb 20, 2021

as it says on the tin

@phadej phadej added the help wanted Extra attention is needed label Feb 20, 2021
@phadej
Copy link
Owner

phadej commented Feb 20, 2021

That is somewhat expected, and I don't have any ideas nor plans to fix this myself.

@phadej
Copy link
Owner

phadej commented Feb 21, 2021

One idea, which requires heavy development work, is to make ghci:s :browse and :doc amenable for machine consumption. Then cabal-docspec could :browse the modules (including re-exported ones) and find examples in :doc to test.

This is how Python's doctest works: by reflection, not by looking at the source files directly. (AFAIK).

To be clear, I won't work on the GHC part, that is my wish as tooling writer though.

@sjakobi
Copy link

sjakobi commented Feb 22, 2021

One idea, which requires heavy development work, is to make ghci:s :browse and :doc amenable for machine consumption. Then cabal-docspec could :browse the modules (including re-exported ones) and find examples in :doc to test.

https://gitlab.haskell.org/ghc/ghc/-/issues/15461 seems somewhat related.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants