Commit f2b2800

authored

update for rustc_intrinsic_const_stable_indirect (#2138)

1 parent b679e71 commit f2b2800Copy full SHA for f2b2800

File tree

-2

lines changed

-2

lines changed

Lines changed: 3 additions & 2 deletions

Original file line number	Diff line number	Diff line change
@@ -57,6 +57,7 @@ ipsum")]` has the same interface as the `unstable` attribute. It is used to mark
`57`	`57`	- If a `const fn` makes use of unstable language features or intrinsics.
`58`	`58`	`(The compiler will tell you to add the attribute if you run into this.)`
`59`	`59`	- If a `const fn` is `#[stable]` but not yet intended to be const-stable.
	`60`	`+- To change the feature gate that is required to call a const-unstable intrinsic.`
`60`	`61`
`61`	`62`	`Const-stability differs from regular stability in that it is recursive: a`
`62`	`63`	`#[rustc_const_unstable(...)]` function cannot even be indirectly called from stable code. This is
`@@ -79,10 +80,10 @@ compiler features); the only reason it is not const-stable yet are API concerns.`
`79`	`80`	`This should also be added to lang items for which const-calls are synthesized in the compiler, to`
`80`	`81`	`ensure those calls do not bypass recursive const stability rules.`
`81`	`82`
`82`		`-## rustc_const_stable_intrinsic`
	`83`	`+## rustc_intrinsic_const_stable_indirect`
`83`	`84`
`84`	`85`	`On an intrinsic, this attribute marks the intrinsic as "ready to be used by public stable functions".`
`85`		-The `rustc_const_unstable` can be removed when this attribute is added.
	`86`	+If the intrinsic has a `rustc_const_unstable`attribute, it should be removed.
`86`	`87`	`Adding this attribute to an intrinsic requires t-lang and wg-const-eval approval!`
`87`	`88`
`88`	`89`	`## rustc_default_body_unstable`

Comments

(0)