Update state_dict docs

[Atcold]

• Better definition of state_dict
• Additional shallow copy warning

[facebook-github-bot]

:link: Helpful links

• :test_tube:  See artifacts and rendered test results at hud.pytorch.org/pr/83104
• :page_facing_up:  Preview Python docs built from this PR
• :page_facing_up:  Preview C++ docs built from this PR
• :question:Need help or want to give feedback on the CI? Visit our office hours

:white_check_mark: No Failures (0 Pending)

As of commit c3bc848d3a (more details on the Dr. CI page):

Expand to see more

---

:green_heart: :green_heart: Looks good so far! There are no failures yet. :green_heart: :green_heart:

---

This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

[Atcold]

Also, related (maybe I should create a separate issue), add a copy() method to the state_dict 'object'. It doesn't make sense to import another library (copy) to make a copy of a network's state.

[jbschlosser]

@pytorchbot merge

[pytorchmergebot]

@pytorchbot successfully started a merge and created land time checks. See merge status here and land check progress here.

[github-actions[bot]]

Hey @Atcold. You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'. For changes that are 'topic: not user facing' there is no need for a release notes label.

[Atcold]

Why do PRs get closed rather than merged?

[soumith]

just an infrastructure thing