-
Notifications
You must be signed in to change notification settings - Fork 26
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
Fixed closure import problem when defining a library #336 #337
Conversation
Minor comment: You don't need to write the diff in the description, since it's already visible under "Files changed". I'd rather see a more high level description of what was done ("Added more cases" doesn't tell me anything useful). No need to fix it for this PR though as we were all in the room when it was fixed :) |
The big question is who will merge this, as most of us were in the room when it was written! 😮 |
:)), may be Tobias or Dave, or one of us? But anyway, do we need a testcase with the expected result ? |
|
Test case is added. |
Great, is everyone fine with merging this? |
yes! |
It's best to squash the two commits into one so that you could learn how to use rebase. |
+1 |
@PhucVH888 what's the status of squashing these two commits? |
These commits have not been squashed yet. I think it would be nice if you or @albertnetymk can show me how to do this tomorrow. |
I agree but first I would recommend that you read the official doc on rebase and, if you are still unsure, we solve your doubts. The important step is that you get a better understanding of the |
I have squashed these two commits. |
Fixed closure import problem when defining a library #336
We have fixed this problem by adding more cases to due with
import
inUtils.hs