docs:Update rustc-dev-guide-book

[QingyaoLin]

Rename StringReader to Lexer and update links.

The StringReader struct link is invalid since pr:Merge TokenTreesReader into StringReader.

[rustbot]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @lcnr (or someone else) some time within the next two weeks.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

• @rustbot author: the review is finished, PR author should check the comments and take action accordingly
• @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

[rustbot]

The rustc-dev-guide subtree was changed. If this PR only touches the dev guide consider submitting a PR directly to rust-lang/rustc-dev-guide otherwise thank you for updating the dev guide with your changes.

cc @BoxyUwU, @jieyouxu, @Kobzol

[QingyaoLin]

This is the commit record for the StringReader changes I found in git log:

> git log -S 'struct StringReader' -- .\compiler\rustc_parse
commit 98777b4c490386ab7889718e811d28ce7423f0af
Author: Nicholas Nethercote <n.nethercote@gmail.com>
Date:   Thu Nov 14 16:55:27 2024 +1100

    Merge `TokenTreesReader` into `StringReader`.

[QingyaoLin]

Since I'm working on Windows, I also can't build rustc-dev-guide, so I don't know why it doesn't detect that StringReader is a dead link. ( rustc-dev-guide uses mdbook-linkcheck2 to detect invalid links)

Does this mean that mdbook-linkcheck2 is a potential bug?

[QingyaoLin]

What happened here？

[Kobzol]

You pushed a merge commit; instead, you should use rebases, as per the guide in the comment above.

[QingyaoLin]

Fixed in rust-lang/rustc-dev-guide#2208

[Kobzol]

In general, if a PR only modifies rustc-dev-guide, it should be sent against that repository.

[QingyaoLin]

In general, if a PR only modifies rustc-dev-guide, it should be sent against that repository.一般来说，如果 PR 仅修改 rustc-dev-guide，则应针对该存储库发送它。

How should this be done? I don't quite understand how a PR for a large repository containing multiple sub-repositories should be targeted to the sub-repositories.

Can I do this directly in the rust-lang-rust repository, or should I clone it separately and modify the subrepo and pull the PR?
This seems to have a huge sense of disconnection.

[Kobzol]

If you only modify the code of a subtree (e.g. rustc-dev-guide), the PR should be made directly against the repository of the subtree repo (https://github.com/rust-lang/rustc-dev-guide). We regularly sync the code changes between rustc and the subtree repos.

We tried to document this better in #135770.

[QingyaoLin]

Thanks，I understand.