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

[Bug] Instance Translator cannot properly set exact scope for top-level signatures more than one #100

Closed
ferhaterata opened this issue May 29, 2017 · 1 comment

Comments

@ferhaterata
Copy link
Member

ferhaterata commented May 29, 2017

sig Requirement {
	requires: set Requirement,
	refines: set Requirement,
	contains: set Requirement,
	partiallyRefines: set Requirement,
	conflicts: set Requirement,
	equals: set Requirement
}

sig Implementation {
	satisfy: set Requirement,
	refines: set Implementation,
}

The scope fragment of generated Alloy code for above top-level signatures using Reason@relation and ConsistencyChecking functions is in the following:

...
pred show{}
run show for
exactly 14 Requirement

Instead, that should be as in the following:

...
pred show{}
run show for
exactly 14 Requirement, 0 Implementation
@ferhaterata
Copy link
Member Author

There is no bug. False Alarm because of the user changed the specification without uploading the specification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants