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

README: Document the reasons/uses of each type of example #784

Merged
merged 1 commit into from
Dec 17, 2018
Merged

README: Document the reasons/uses of each type of example #784

merged 1 commit into from
Dec 17, 2018

Conversation

petertseng
Copy link
Member

Although the README listed the three types that were proposed and
accepted in #397, it failed to
explain when we would want to use each type.

We rectify this by explaining each type.

Checks the first box (consider/document/discuss) of
#783

* error: The example is expected to fail to build.
* There is only one intended use of this so far, and that is a single check that a solution without a type signature will fail to build (because CI builds with `--pedantic`).
Copy link
Member Author

Choose a reason for hiding this comment

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

Aside: This is of questionable usefulness as actionable information for us, as explained as follows:

If the error-nosig example ever successfully builds, that means there is a problem with stack --pedantic. What would we do differently in that situation?

Wait for stack to solve this problem, potentially reporting it if nobody has before?

We would have to be on our guard that other instances of --pedantic are not being respected, I suppose? So, the single error example sort of serves as a canary in the cole coal mine?

So I guess it's useful info, but given that the most likely mode of failure is out of our control, having that cause all further CI to fail would be unfortunate. My ideal would be keeping the information available but not having it break CI.

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't mind that we have it now that we do.

Copy link
Contributor

@sshine sshine 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 documenting this.

Although the README listed the three types that were proposed and
accepted in #397, it failed to
explain when we would want to use each type.

We rectify this by explaining each type.

Checks the first box (consider/document/discuss) of
#783
@sshine
Copy link
Contributor

sshine commented Dec 17, 2018

Should we merge this now?

@petertseng petertseng merged commit 76cd537 into exercism:master Dec 17, 2018
@petertseng petertseng deleted the example-types branch December 17, 2018 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants