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.

Sign up for GitHub

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

Jump to bottom

Build a proper compilation unit #109

Open
slarse opened this issue Apr 20, 2020 · 2 comments
Open

Build a proper compilation unit #109

slarse opened this issue Apr 20, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@slarse
Copy link
Collaborator

slarse commented Apr 20, 2020

Spork currently does not care about the compilation units in the merge, but as the recent refactorings unified the factory for all elements, it shouldn't be hard to also merge compilation units (including comments), and then print the compilation unit.

In the future, Spork could be extended to deal with multiple compilation units.
@slarse slarse added the enhancement New feature or request label Apr 20, 2020
@slarse
Copy link
Collaborator Author

slarse commented Apr 25, 2020

It seems like this may be less convenient than I thought

@slarse
Copy link
Collaborator Author

slarse commented May 5, 2020

This is a stretch goal, and probably necessary for being able to use Spork well for analysis, but I just don't have the time to do this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@slarse