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

Towards a more complete Analysis.Export #50

Open
chkl opened this issue Mar 9, 2018 · 0 comments
Open

Towards a more complete Analysis.Export #50

chkl opened this issue Mar 9, 2018 · 0 comments

Comments

@chkl
Copy link

chkl commented Mar 9, 2018

Hi everyone,

I was already talking a bit with lambdageek on reddit (InformalInflation, that's me). In short, I have this use case where I would like to apply some tranformations to a C file after type checking. (I need the type information to perform the transformations). As lambdageek pointed out, I should probably do this on the SemRep and not on the AST.

So, after applying my transformation on SemRep I still need to pretty-print it back into the file. I believe that is what Analysis.Export is for.

I saw the warning:

WARNING : This is just an implementation sketch and not very well tested.

And well, if I am not mistaken, there's no top-level function like exportSemRep :: GlobalDecls -> CTranslUnit, which would be what I need.

Before I start adding functions towards the goal, is there something I should know?

tl;dr: I would like to contribute to Analysis.Export, what do I need to know?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant