You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for giving Claro a try! You've run into a known type checking bug unfortunately. There are some rough edges around Claro's current handling of oneof<...>s in circumstances like this one. Essentially the issue is that Claro's type checking logic is essentially just doing a plain type equality check in this instance ([int] != oneof<[int], int>) whereas it should obviously accept either variant in this case just as it does with the variable assignment.
Even procedure arguments have addressed this issue, as the below works as well:
Awesome, thanks for getting back to me! I'm enjoying Claro so far! Learning Bazel is also new to me but I'm very impressed by how much it can accomplish (learning curve is there though)
The following does not compile giving
Invalid type: Found: LIST Expected: oneof<[int], int>
Introducing a variable allows it to compile
Is this intended?
The text was updated successfully, but these errors were encountered: