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
I really don't feel that Exceptions serve to enhance the understandability of a program's flow of control. So I don't want to build Claro around exceptions. Instead, I think procedures should return error values in results so that programmers can directly check for success. This leads to some super gross code without pattern matching, so for this reason alone I find enough justification to implement pattern matching. As an incredible bonus, Claro will also get the incredible expressivity that pattern matching gives a language in the general case, not even considering error handling.
I really don't feel that Exceptions serve to enhance the understandability of a program's flow of control. So I don't want to build Claro around exceptions. Instead, I think procedures should return error values in results so that programmers can directly check for success. This leads to some super gross code without pattern matching, so for this reason alone I find enough justification to implement pattern matching. As an incredible bonus, Claro will also get the incredible expressivity that pattern matching gives a language in the general case, not even considering error handling.
Should look something like Rust syntax: https://doc.rust-lang.org/book/ch18-03-pattern-syntax.html
The text was updated successfully, but these errors were encountered: