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

Diplomacy Tutorial: make it clear how to execute it #2664

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

mwachs5
Copy link
Contributor

@mwachs5 mwachs5 commented Oct 12, 2020

Add more instructions to the Diplomacy tutorial that make it more "doing" vs "reading". Needed to clarify both how to build the docs or how to copy-and-paste and execute the code by making another main.

Related issue:

Type of change: other enhancement

Impact: no functional change

Development Phase: implementation

Release Notes

Copy link
Contributor

@debs-sifive debs-sifive left a comment

Choose a reason for hiding this comment

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

Not sure if you think this is a useful idea... But what if we put an invisible code block at the top of the tutorial with a comment like

/** ATTENTION: if you can read this, you are reading raw documentation. Please generate
  * documentation from this source file as described in the docs/README.md.
  */

So then if someone stumbles across the source docs, they know they are reading the wrong thing? I was super confused by generated versus raw docs in our private repo.

call it with `sbt`:

``` scala mdoc:silent
/** MAIN */
Copy link
Contributor

Choose a reason for hiding this comment

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

Can probably take out this comment b/c it doesn't add much.

Copy link
Contributor

Choose a reason for hiding this comment

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

(Referring to /**MAIN*/)

@mwachs5
Copy link
Contributor Author

mwachs5 commented Oct 13, 2020

I was JUST thinking that we should put a comment like that... as I was reading the source and confused by the printf at the end

@sequencer sequencer self-requested a review June 15, 2022 19:51
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.

None yet

2 participants