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

Parser Fixes #467

Closed
3 tasks
iamrecursion opened this issue May 7, 2020 · 0 comments
Closed
3 tasks

Parser Fixes #467

iamrecursion opened this issue May 7, 2020 · 0 comments
Labels
--breaking Important: a change that will break a public API or user-facing behaviour

Comments

@iamrecursion
Copy link
Contributor

iamrecursion commented May 7, 2020

Summary

The current parser is in a pretty buggy state, and needs a lot of things fixed in it. This is going to take place as a two-part effort. Part 1 will involve fixing urgent issues in the current parser implementation, while part 2 will involve migrating to the new parser implementation.

Value

We will be able to deal with the language syntax in a far better way.

Specification

Acceptance Criteria & Test Cases

  • The entire above specification has been completed.
  • None of the tasks have resulted in functional regressions.
@iamrecursion iamrecursion transferred this issue from another repository Jun 23, 2020
@joenash joenash added Category: Syntax --breaking Important: a change that will break a public API or user-facing behaviour labels Jun 23, 2020
@iamrecursion iamrecursion mentioned this issue Jun 23, 2020
26 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
--breaking Important: a change that will break a public API or user-facing behaviour
Projects
None yet
Development

No branches or pull requests

2 participants