-
-
Notifications
You must be signed in to change notification settings - Fork 195
Making the Haskell track more gradual #193
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
Comments
Comment from a user about
|
I went through and tried to write down a few notes for each exercise. Each line has the exercise name, a space, then a list of notes. I could not be exhaustive, and for some exercise I was too lazy to figure out what to write so I only wrote "?" Stars mean I think the exercise is quite involved. I don't know how useful this list will be. It is likely it will be need to be improved and completed. I would say big things to pay attention to are the problem that use the IO monad, and stuff I marked with stars.
|
Thank you very much, @petertseng! 👍 I'll be forced to take another at each of the problems to rewrite test suites to fail-fast with |
Also check out the blog post by @IanWhitney |
Great post! Thanks! |
With the new Considering that this issue is dead for more almost two months, I will close it so e can focus on what needs to be done now! #274 I anyone opposes, I'll immediately reopen it. |
Making the Haskell track more interesting for beginners #192
Making the Haskell track more gradual
Anyone would like to take the humongous task of solving at least part of this?
If we did this at least for the first 20 exercises it would be nice. If we did this for the entire track it would be fantastic.
The text was updated successfully, but these errors were encountered: