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

Is there a tool to update the data/baseEnvironment files? #107

Open
ddssff opened this issue May 9, 2018 · 3 comments
Open

Is there a tool to update the data/baseEnvironment files? #107

ddssff opened this issue May 9, 2018 · 3 comments
Labels

Comments

@ddssff
Copy link
Contributor

ddssff commented May 9, 2018

The files are two+ years old - i would think they could get out of date?

@chshersh
Copy link
Contributor

@ddssff I'm not aware of such tool. Maybe @phischu can elaborate how those files were generated initially.

When I was working on importify project I've implemented my own caching of symbols for Hackage packages. But it's doesn't work well for base package because it has a lot of CPP and a lot of primitive Haskell and other fancy stuff so haskell-src-exts can't handle it properly 😞

@ddssff
Copy link
Contributor Author

ddssff commented May 12, 2018

It looks like the getModuleExports function from the hint package will help.

@ddssff
Copy link
Contributor Author

ddssff commented May 13, 2018

I submitted a PR that addresses this issue. It eliminates the need for a hard coded symbol base. I've only tested in on Prelude so far. (Well, I thought I submitted it.)

ddssff added a commit to ddssff/haskell-names that referenced this issue May 13, 2018
…tion

findModuleSymbols, which generates a list of the modules in a named
modules using template haskell and the hint package.  Should close issue haskell-suite#107.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants