rfcs
rfcs copied to clipboard
RFC 1020: Multi choice control flow
One might say that this is not big enough change for a RFC, but hey let me have my fun.
I intentionally didn't push match in RFC title, because this is subject of the discussion.
My major concern would be using ==
operator rather than full-blown pattern matching:
- We mentioned somewhere that we probably want to implement algebraic types somehow at some point
- Even without that it would be nice to match by string prefix, array patterns, and numeric ranges (Rust can do all these things, for example)
rather than full-blown pattern matching
Yes, agree. The RFC does not even solve what the issue that requested it. My intention was to make something quick and extend it later.
Problem with that is that we should at least decide on syntax for pattern matching, otherwise we will probably run into backward incompatibility when adding it later.
Compiler team agrees that this RFC can wait and be extended to do pattern matching when algebraic types are a thing.