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
  • #20

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

Support `where` clauses

Currently, if someone has a where clause in their module, it's turned into a let binding. This is because the compiler desugars where clauses during parsing.

This issue is blocked on the compiler supporting where clauses that aren't desugared in parsing because we should not maintain a different parser from the official one if we can at all help it. We can't do anything about it, but we should still track that it's a thing we want to support.

Related issues

Assignee
Assign to
1.0.0
Milestone
1.0.0
Assign milestone
Time tracking
None
Due date
No due date
2
Labels
bug feature
Assign labels
  • View project labels
Reference: joneshf/purty#20