Skip to content
This repository has been archived by the owner on Mar 18, 2019. It is now read-only.

Add happy to alternatives. #9

Closed
wants to merge 1 commit into from
Closed

Add happy to alternatives. #9

wants to merge 1 commit into from

Conversation

vic
Copy link

@vic vic commented Jun 20, 2016

Add link to happy.

@vic
Copy link
Author

vic commented Jun 20, 2016

OMG just realised kase is a ruby project haha, so maybe it makes no sense to link to happy.

@vic vic closed this Jun 20, 2016
@lasseebert
Copy link
Owner

Hehe, no that probably don't make much sense. Not as an "alternative" at least, although the problem it solves is similar to Kase :)

I had a look at Happy and it seems very nice at error handling nested case situiations. How does it differ from the new with-else in Elixir 1.3? (ref: http://tuvistavie.com/2016/elixir-1-3/#with-on-steroids)

@vic
Copy link
Author

vic commented Jun 20, 2016

Not much difference actually. with special form being included in elixir will get lot more users I guess.

I started working on happy before 1.3 after exploring with ok_jose and as I mention on the readme I wanted something easy to the eyes without requiring to be mindful about the form syntax - I still don't like the way you have to place a comma after each pattern match and the use of <-, not that users wont get used to it with the time, but I just don't happen to like that much. - In happy your code is basically the elixir you already know with each pattern match (except simple assignment) transformed into a case. The downside of happy is it may leak variables and with wont. So far I'm using my library to some prod code of mine, and have been pretty much happy with it haha.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants