Skip to content
This repository has been archived by the owner on Sep 7, 2023. It is now read-only.

Namespace handling #18

Closed
jeromesimeon opened this issue Mar 5, 2018 · 1 comment
Closed

Namespace handling #18

jeromesimeon opened this issue Mar 5, 2018 · 1 comment
Labels
Type: Bug 🐛 Something isn't working
Projects
Type Checking Contract Modularity
Milestone
Typing Support

Comments

@jeromesimeon
Copy link
Member

jeromesimeon commented Mar 5, 2018 •
edited
Loading

Some review/consolidation of the namespace handling in Ergo should happen. The top-level package declaration indicates a namespace for the given Ergo file. The namespace needs to be properly taken into account in type declarations, function/clause calls, etc.
@mttrbrts mttrbrts mentioned this issue Mar 6, 2018
Closed
@jeromesimeon jeromesimeon added the Type: Bug 🐛 Something isn't working label Mar 9, 2018
This was referenced Apr 23, 2018
Merged
Closed
Closed
@jeromesimeon jeromesimeon added this to the Type checking support milestone May 6, 2018
@jeromesimeon jeromesimeon added this to In progress in Type Checking May 9, 2018
This was referenced Jun 14, 2018
Closed
Merged
@jeromesimeon jeromesimeon mentioned this issue Jun 29, 2018
Merged
@jeromesimeon
Copy link
Member Author

Handled in PR #250

@jeromesimeon jeromesimeon moved this from In progress to Done in Type Checking Jul 23, 2018
@jeromesimeon jeromesimeon mentioned this issue Jul 24, 2018
Closed
6 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Type: Bug 🐛 Something isn't working
Projects
Contract Modularity
  
Done
Type Checking
  
Done
Milestone
Typing Support
Development

No branches or pull requests
1 participant
@jeromesimeon