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

What we need to send to nostarch for changes #1607

Closed
18 of 20 tasks
carols10cents opened this issue Nov 1, 2018 · 5 comments
Closed
18 of 20 tasks

What we need to send to nostarch for changes #1607

carols10cents opened this issue Nov 1, 2018 · 5 comments

Comments

@carols10cents
Copy link
Member

carols10cents commented Nov 1, 2018

I'm making a list of what I've found that has changed between the first printing and 2018-edition that we need to tell nostarch we want to change, I want to make sure I get everything. I haven't actually looked at all of this yet, just trying to get a handle on it.

There are some questions for you throughout @steveklabnik, also lmk if there's anything missing that you can think of?

Large sections of new text:

  • Appendix D: Useful Development Tools
  • Appendix E: Editions
  • Whole chapter 7, now called "Packages, Crates, and Modules"
  • New section 19-06 on macros

Smaller changes:

  • Scrap the macros appendix D
  • Go through all open PRs and see if we want to merge and include any of them
  • nostarch/version-note.md What version we're pinning these updates to (1.31)
  • nostarch/appendix-a-new-section.md Keywords appendix A
  • nostarch/chapter10-traits-as-parameters.md 10-02: new "Traits as Parameters" section, new "Returning Types that Implement Traits" section, some other impl trait changes throughout
  • Small typo fixes, etc that I'm gathering as comments on the laid out PDF
  • 11-01: new "Using Result<T, E> in tests" section
  • Removing explicit --bin with cargo new calls
  • 12-02, 20-01: fs:read_to_string changes
  • 12-03, 17-02, 17-03, 19-02, 19-04: dyn additions
  • 15-02: MyBox heap caveat
  • 18-03: new "Destructuring Nested Structs & Enums" section, remove "Creating References in Patterns with ref and ref mut" section (or moving to "Legacy patterns: ref and ref mut" section?)
  • 19-01: slice alignment caveat
  • 19-02: new "The anonymous lifetime" section
  • 19-05: new map/() initializer syntax example
  • 20-02: sleep browser behavior caveat
@steveklabnik
Copy link
Member

I believe you have all the big bits; I went through and diff'd 2018 and second edition a few weeks ago and all of this looks about right

Regarding questions:

Add the other useful tools appendix G? Or is this an online-only appendix?

IMO, we should include it.

Add the editions appendix H? Or is this an online-only appendix?

IMO, we should include it.

What version we're pinning these updates to (1.30? 1.31?)

1.31, that's the first 2018 release

Scrap the macros appendix D, right?

Yep!

remove "Creating References in Patterns with ref and ref mut" section (or moving to "Legacy patterns: ref and ref mut" section?)

I'd be happy with either approach, to be honest. Maybe since we have the text, for now they go to "legacy".

@carols10cents
Copy link
Member Author

I'd be happy with either approach, to be honest. Maybe since we have the text, for now they go to "legacy".

I think we should take it out. ref was always confusing anyway, and we don't discuss other legacy things like try!.

@eddyp
Copy link
Contributor

eddyp commented Nov 18, 2018

Is there any reference or mention about embedded support? I know the 2018-edition had embedded support as a goal, but having an interest in this area, I found only some info in the first edition. I know it is something that should not the in the introduction book to rust, but some mention and a pointer to other docs/info/site could be useful.

@carols10cents
Copy link
Member Author

@eddyp The working groups for the command line, wasm, networking, and embedded areas that we're spotlighting with the 2018 edition are all implemented as crates, not in the language or the standard library itself. They're all still evolving quickly as well! That makes these areas not great candidates for inclusion in the book itself.

The good news is that each of the subject areas is writing their own book, and they're going to be featured prominently on the new rust-lang.org website. You can check out the embedded rust book here and keep your eye out for an alpha announcement about the new website this week :)

@carols10cents
Copy link
Member Author

Hoookay I think I got everything for this round at least.

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

No branches or pull requests

3 participants