-
Notifications
You must be signed in to change notification settings - Fork 6
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
Resolution of methods with list parameters not working #20
Labels
Comments
It looks like the issue only occurs when the Sequence is declared within an operation. e.g. the following code is correctly checked & interpreted:
|
echebbi
added a commit
that referenced
this issue
Oct 14, 2019
Because: - Sequences declared in operations could not be used as arguments of other operations (that was causing an error at runtime). How: - Sequences in extension (e.g. Sequence{1, 2, 3}) are evaluated by AQL as ArrayList instances. Hence, sequences declared in operations with the extension syntax were assigned an ArrayList value, whereas they are expecting to hold an EList instance.
6 tasks
echebbi
added a commit
that referenced
this issue
Nov 22, 2019
Why: - unable to call a method taking a Sequence as parameters - unable to use a parameter of type Sequence within an operation How: - store method parameters' generic type when building the AST - turn signature of methods expecting Sequence into 'foo(Sequence<T>)' instead of 'foo(EList<T>)' Signed-off-by: Emmanuel Chebbi <emmanuel.chebbi@outlook.fr>
echebbi
added a commit
that referenced
this issue
Nov 22, 2019
Why: - unable to call a method taking a Sequence as parameters - unable to use a parameter of type Sequence within an operation How: - store method parameters' generic type when building the AST - turn signature of methods expecting Sequence into 'foo(Sequence<T>)' instead of 'foo(EList<T>)' Signed-off-by: Emmanuel Chebbi <emmanuel.chebbi@outlook.fr>
dvojtise
pushed a commit
that referenced
this issue
Dec 6, 2019
Why: - unable to call a method taking a Sequence as parameters - unable to use a parameter of type Sequence within an operation How: - store method parameters' generic type when building the AST - turn signature of methods expecting Sequence into 'foo(Sequence<T>)' instead of 'foo(EList<T>)' Signed-off-by: Emmanuel Chebbi <emmanuel.chebbi@outlook.fr>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
When using lists (or sequences in ALE) as parameters for a method, the engine is unable to resolve the right method to use.
For example, the following minimal behavior file:
Returns the following output:
The text was updated successfully, but these errors were encountered: