diff options
| author | Dylan DPC <99973273+Dylan-DPC@users.noreply.github.com> | 2023-01-23 11:52:04 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-01-23 11:52:04 +0530 |
| commit | 28081a6aa6a13199e6ee3c09ab544139eb23a3fa (patch) | |
| tree | 5a7408ed472ff3e8de6d2446862eb0157609d795 /tests/rustdoc-js-std/parser-errors.js | |
| parent | 3d4c3125bebdcc8a4cc6de2a9925c7259fde2b63 (diff) | |
| parent | 33696fa9cab5bec947147d65833233b957b5edd5 (diff) | |
| download | rust-28081a6aa6a13199e6ee3c09ab544139eb23a3fa.tar.gz rust-28081a6aa6a13199e6ee3c09ab544139eb23a3fa.zip | |
Rollup merge of #106854 - steffahn:drop_linear_arc_rebased, r=Mark-Simulacrum
Add `Arc::into_inner` for safely discarding `Arc`s without calling the destructor on the inner type. ACP: rust-lang/libs-team#162 Reviving #79665. I want to get this merged this time; this does not contain changes (apart from very minor changes in comments/docs). See #79665 for further description of the PR. The only “unresolved” points that led to that PR being closed, AFAICT, were * The desire to also implement a `Rc::into_inner` function * however, this can very well also happen as a subsequent PR * Possible need for further discussion on the naming “`into_inner`” (?) * `into_inner` seems fine to me; also, this PR introduces unstable API, and names can be changed later, too * ~~I don't know if a tracking issue for the feature flag is supposed to be opened before or after this PR gets merged (if *before*, then I can add the issue number to the `#[unstable…]` attribute)~~ There is a [tracking issue](https://github.com/rust-lang/rust/issues/106894) now. I say “unresolved” in quotation marks because from my point of view, if reviewers agree, the PR can be merged immediately and as-is :-)
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions