Skip to content
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

Add comments to indicate where imports can be added #53

Merged

Conversation

bulters
Copy link
Contributor

@bulters bulters commented Jan 29, 2022

This is to fix issue #52

@chshersh chshersh added documentation Improvements or additions to documentation tests labels Jan 29, 2022
Copy link
Member

@chshersh chshersh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for improving the docs! I have only one suggestion 🙂

src/Lecture3.hs Outdated
Comment on lines 37 to 39
{- | If you need to import libraries, do it after this line ... -}

{- | ... and before this line. Otherwise the test suite might fail -}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need to have such a comment only in this file. Because only this module has the $setup part that needs to happen after imports. The rest are fine 🙂

Also, I've added some arrows to attract more attention 👀

Suggested change
{- | If you need to import libraries, do it after this line ... -}
{- | ... and before this line. Otherwise the test suite might fail -}
{- VVV If you need to import libraries, do it after this line ... VVV -}
{- ^^^ ... and before this line. Otherwise, the test suite might fail ^^^ -}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My reasoning for adding them to all files was:

  1. Instructional: show people where it is customary to add imports.
  2. Non-spoilery: I think Lecture3.hs is the first set of exercises where importing a library might make it easier, but no need to give that away?

Like the arrows ;-)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bulters Makes sense 🙂 I agree with that. In that case, if you could add arrows to all newly introduced sections, happy to merge 👍🏻

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

Copy link
Member

@chshersh chshersh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! 👍🏻

@chshersh chshersh merged commit f80ad5a into haskell-beginners-2022:main Jan 31, 2022
marcgreen pushed a commit to marcgreen/exercises that referenced this pull request Feb 13, 2022
…s-2022#53)

* Add comments to indicate where imports can be added

* Add arrows to indicate where imports can be added

Co-authored-by: Dmitrii Kovanikov <kovanikov@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants