-
Notifications
You must be signed in to change notification settings - Fork 11
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
value bug with wildcard? #421
Comments
(I just edited the example slightly to make it clearer) |
ah! the plot thickens:
|
Ok, so this is extremely confusing, but not a bug. The input bundle is
and the program is
The first line of the program produces a binding of
Then, when There is a bug here--it's that |
why does value do pattern matching with the wild card? I think only |
did you see the second issue?
|
or is that similar, that |
@ramagottfried, I think you're right that pattern matching in o.expr should be explicit, rather than implicit. I just checked the history, and this behavior has been there forever, so this would be a breaking change, although, I'm not sure anyone relies on it. I'm going to add this to the 1.4 list--I think it's too late to consider something as deep as this for 1.3. |
@maccallum cool, that sounds good -- I'm fairly sure that not many people are using the hidden pattern matching functionality, since as far as I know there is no example of this in the documentation, I only stumbled on it when trying to operate on a wildcard address (that was then being sent to another process where the matching happens). |
not sure what's going on here exactly -- any ideas? is it a bug? I think it might be.
The text was updated successfully, but these errors were encountered: