rust/compiler/rustc_codegen_gcc/example, branch 1.85.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.85.02024-12-07T20:50:00+00:00Make `Copy` unsafe to implement for ADTs with `unsafe` fields2024-12-07T20:50:00+00:00Jack Wrennjack@wrenn.fyi2024-12-06T17:11:36+00:00urn:sha1:3ce35a4ec5f06828f908a018da083af5eb54301a
As a rule, the application of `unsafe` to a declaration requires that use-sites
of that declaration also require `unsafe`. For example, a field declared
`unsafe` may only be read in the lexical context of an `unsafe` block.
For nearly all safe traits, the safety obligations of fields are explicitly
discharged when they are mentioned in method definitions. For example,
idiomatically implementing `Clone` (a safe trait) for a type with unsafe fields
will require `unsafe` to clone those fields.
Prior to this commit, `Copy` violated this rule. The trait is marked safe, and
although it has no explicit methods, its implementation permits reads of `Self`.
This commit resolves this by making `Copy` conditionally safe to implement. It
remains safe to implement for ADTs without unsafe fields, but unsafe to
implement for ADTs with unsafe fields.
Tracking: #132922
remove support for rustc_safe_intrinsic attribute; use rustc_intrinsic functions instead2024-11-08T08:16:00+00:00Ralf Jungpost@ralfj.de2024-11-07T07:59:43+00:00urn:sha1:e3010e84dbf2e06424c91c5a3d4206c1911813bdRename Receiver -> LegacyReceiver2024-10-22T12:55:16+00:00Adrian Tayloradetaylor@chromium.org2024-09-11T12:27:08+00:00urn:sha1:8f85b90ca6d57459eb19accb6aaf781dd1c7bf6c
As part of the "arbitrary self types v2" project, we are going to
replace the current `Receiver` trait with a new mechanism based on a
new, different `Receiver` trait.
This PR renames the old trait to get it out the way. Naming is hard.
Options considered included:
* HardCodedReceiver (because it should only be used for things in the
standard library, and hence is sort-of hard coded)
* LegacyReceiver
* TargetLessReceiver
* OldReceiver
These are all bad names, but fortunately this will be temporary.
Assuming the new mechanism proceeds to stabilization as intended, the
legacy trait will be removed altogether.
Although we expect this trait to be used only in the standard library,
we suspect it may be in use elsehwere, so we're landing this change
separately to identify any surprising breakages.
It's known that this trait is used within the Rust for Linux project; a
patch is in progress to remove their dependency.
This is a part of the arbitrary self types v2 project,
https://github.com/rust-lang/rfcs/pull/3519
https://github.com/rust-lang/rust/issues/44874
r? @wesleywiser
stabilize raw_ref_op2024-08-18T17:46:53+00:00Ralf Jungpost@ralfj.de2024-07-13T11:53:56+00:00urn:sha1:79503dd742253cdca54f10aec9052ff477ccaf38Fixes in various places2024-08-10T10:08:46+00:00Nadrierilnadrieril+git@gmail.com2024-03-20T21:51:29+00:00urn:sha1:e77612d3e4ff34d5096fbf7f8a1b9d3a4351770cstabilize `is_sorted`2024-07-27T19:11:54+00:00Slanternsslanterns.w@gmail.com2024-07-27T17:28:39+00:00urn:sha1:ec0b3540925af3cab9c38b0344902d48edb9d5b8Remove lang feature for type ascription2024-07-12T00:40:38+00:00Michael Gouletmichael@errs.io2024-07-11T22:57:56+00:00urn:sha1:a36fcc8969761fa08c8f969104bba500ff0fb75cMerge commit '98ed962c7d3eebe12c97588e61245273d265e72f' into master2024-07-10T10:44:23+00:00Guillaume Gomezguillaume.gomez@huawei.com2024-07-10T10:44:23+00:00urn:sha1:7cbe50e2098c35fda06433cd36bbced941607317Step bootstrap cfgs2024-05-02T02:19:11+00:00Mark Rousskovmark.simulacrum@gmail.com2024-04-29T13:27:34+00:00urn:sha1:a64f94161130944f8fda1f6dcc00f37860f43ecfError on using `yield` without also using `#[coroutine]` on the closure2024-04-24T08:05:29+00:00Oli Scherergit-spam-no-reply9815368754983@oli-obk.de2024-04-11T13:15:34+00:00urn:sha1:aef0f4024aec24fd7e53dbc51883457e44fe17ce
And suggest adding the `#[coroutine]` to the closure