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

Ambiguous concept definitions are not highlighted #723

Open
adrianffletcher opened this issue May 16, 2019 · 0 comments
Open

Ambiguous concept definitions are not highlighted #723

adrianffletcher opened this issue May 16, 2019 · 0 comments

Comments

@adrianffletcher
Copy link

When there are two concepts defined with the same name and both are imported into an Ergo file it is not clear which one is being used and there is no warning or error message produced by the compiler.

The attached archive file (which needs to be renamed back to a .cta file to be used) gives an example of this where there are two LineItem concepts defined and it is not clear if the code should compile or not.

There should at minimum be a warning generated by the compiler if it needs to choose between two different concept definitions and consideration should be given to requiring explicit disambiguation in this case.

helloconceptv0.1.zip

@jeromesimeon jeromesimeon transferred this issue from accordproject/template-archive Dec 11, 2019
@jeromesimeon jeromesimeon added this to In progress in Cicero + Ergo 1.0 Dec 13, 2019
@jeromesimeon jeromesimeon moved this from In progress to To do in Cicero + Ergo 1.0 Dec 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Cicero + Ergo 1.0
  
Priority: Medium
Development

No branches or pull requests

2 participants