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

Trace first principles #105

Open
shaunlebron opened this issue Mar 20, 2016 · 0 comments
Open

Trace first principles #105

shaunlebron opened this issue Mar 20, 2016 · 0 comments

Comments

@shaunlebron
Copy link
Collaborator

After 6 months of design and development, I would like to revisit a potentially false assumption made for #102. To this end and to better understand what Parinfer has become and what else it could it be, I wish to formally trace out the genesis of all rules that were added after the first principle of Parinfer's rule system (i.e. lisp's line invariant for formatting).

This will be another block of documentation to complement the other two:

  • the [website] as a presentation of the background, goals, and implications
  • the [design doc] as a guide for what exactly is happening and how, and a sprinkling of why

So this extra addition will cover why and how each rule was made and what some other possible paths are.

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