-
Notifications
You must be signed in to change notification settings - Fork 7
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
Fix type compatibility where casting is needed #395
Fix type compatibility where casting is needed #395
Conversation
69b253d
to
1ea2809
Compare
@@ -133,14 +133,6 @@ impl Deref for TupleConstraint { | |||
} | |||
} | |||
|
|||
impl FromIterator<PrimitiveType> for TupleConstraint { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed this since I found it confusing. I was actually expecting that this would always be turned into AtLeast
constraints instead of Exact
constraints, e.g. when using this on Data Sources.
I think one should rather make this explicit and use the FromIterator
implementation below.
@@ -690,6 +690,7 @@ impl<'a> RuleParser<'a> { | |||
/// predicate name together with its arity. | |||
fn parse_qualified_predicate_name( | |||
&'a self, | |||
constraint_is_lower_bound: bool, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When parsing source declarations, the type annotations are always lower bounds. In other cases like outputs, these requirements might be stricter. (Since import / export directives are WIP, I would not polish this right now as I expect things to change in the parser anyway.)
Fixes #394