Test-run rust project 4

[brson]

Read through the project 4 text and follow the steps as written. The purpose of this is to discover missing information, conflicting information, inconsistencies, and things that can be improved. Then fix them or file issues.

You will find many. No issue is to small. Be detail-oriented.

As you are working and notice problems, either fix them directly in your own talent-plan branch if possible, file issues or write them down.

The projects are intended to pose problems, with gentle suggestions about how to solve them, but not to teach you how to solve them. To learn how to solve the problems, students are intended to read associated "readings" before trying the project. These readings are not written down yet. If you find yourself using a particular resource to learn how to complete the project, make note of that resource in the corresponding "readings" issue for the project.

Do not read the example code on your first work-through of the project, even if you get stuck. Instead ask for help. Later you will go back and read and edit the example code.

This task is divided into two discreet sub-tasks that you may complete separately or together:

• Edit project 4 text Edit rust project 4 text #89
• Edit project 4 code Edit rust project 4 code #90

And another related task that you may want to contribute to:

• Collect readings for project 4 Collect readings for rust project 4 #91

Here are some questions to think about:

• Each project has an overview describing the task, goals and topics. What is missing from this section that is contained in the text? What is mentioned in this section that is not in the text?

• Each project has a described "setup". What extra steps did you need to figure out for yourself that were not described in the text? Were these extra steps too difficult for the target audience?

• The projects begin by asking you to copy the test cases into your own project, then get the project to build without passing the tests. In this project, was that experience an acceptable way to begin the project? What were the most difficult tests to get compiling? What workflow did you use? Did it frustrate you?

• Each project has a "spec" describing the external interface to the project. What parts of the spec were difficult to understand? What parts of the spec are not reflected in the test suite?

• Are you able to complete the project in the sequence described, or did you have to read forward, jump between sections, implement the code partially and come back to it? How can the project be sequenced more naturally?

• Are there implicit steps that frustrated you or felt unfair? How could we gently nudge the reader in the right direction? How could we add an explicit step to fill in the gap?

• Which material was new to you? Which material was not new to you? Which subjects would you have liked to see in this project?

• Were there words or phrases that you didn't understand? Were there sentences that were too long or complex? Can you rewrite them to be simpler?

• Was there text you think should be cut? Text you think should be added?

• Can you fill in any of the missing content yourself?

• What reading material would help you complete this project?