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

Inconsistent Message operator resolution behaviour #1401

Open
antvaset opened this issue Aug 14, 2024 · 0 comments
Open

Inconsistent Message operator resolution behaviour #1401

antvaset opened this issue Aug 14, 2024 · 0 comments
Assignees

Comments

@antvaset
Copy link
Contributor

I've noticed that Message(1, null, '1', 'Message', 'This is a message') (the second argument is null) fails to translate inside of this library:

library TestLib version '1.0.0'

define y: Message(1, null, '1', 'Message', 'This is a message')

and gives Could not resolve call to operator Message with signature (System.Integer,System.Any,System.String,System.String,System.String).

If I add Message(1, false, '1', 'Message', 'This is a message') or Message(1, null as Boolean, '1', 'Message', 'This is a message') (the second argument is of type System.Boolean) to the same library prior to calling Message with null, it compiles successfully, e.g. both of these compile and run successfully:

library TestLib version '1.0.0'

define x: Message(1, false, '1', 'Message', 'This is a message')
define y: Message(1, null, '1', 'Message', 'This is a message')

and

library TestLib version '1.0.0'

define y: Message(1, null as Boolean, '1', 'Message', 'This is a message') + Message(1, null, '1', 'Message', 'This is a message')
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant