re: Ruby – Pattern Matching – Second Impressions VIEW POST

VIEW PARENT COMMENT VIEW FULL DISCUSSION
 

It would break semantics if overloads are allowed in a way that is syntactically valid in older code. So the challenge would be to pick syntax to specify the type signatures that can not occur in old working code.

Finding syntax that doesn't look awful but that is currently invalid would actually likely be the hardest part of adding support for it.

code of conduct - report abuse