Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
purty
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Schedules
  • Registry
    • Registry
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • Hardy Jones
  • purty
  • Issues
  • #35

Closed
Open
Opened Apr 27, 2018 by Hardy Jones@joneshf
  • Report abuse
  • New issue
Report abuse New issue

Make a pretty print AST

The compiler's AST is nice because it's the source of truth. However, it's not so nice in that is has a bunch of mixed levels of information: there's some desugaring that happens, there's some optimizations that happen, there's some metadata mixed in, there's some cases a user can't write, there's some transformations for pretty printing, etc.

We can improve our situation if we take the compiler's AST and immediately convert to an AST that we want to work with. Afterward, we can do whatever optimizations and transformations we want, and print out the thing we want at the end.

Should make transformations like #19 (closed), #31 (closed), and #32 (closed) easier to do.

Related issues

Assignee
Assign to
Release 2018-07-17
Milestone
Release 2018-07-17
Assign milestone
Time tracking
None
Due date
No due date
0
Labels
None
Assign labels
  • View project labels
Reference: joneshf/purty#35