From 13becefbdf62978116b4a0d2a9c4ff396ede4470 Mon Sep 17 00:00:00 2001 From: lcnr Date: Sun, 28 Feb 2021 11:50:02 +0100 Subject: [PATCH] typo --- posts/2021-02-26-const-generics-mvp-beta.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2021-02-26-const-generics-mvp-beta.md b/posts/2021-02-26-const-generics-mvp-beta.md index 542a0aecf..e385f1bfc 100644 --- a/posts/2021-02-26-const-generics-mvp-beta.md +++ b/posts/2021-02-26-const-generics-mvp-beta.md @@ -90,7 +90,7 @@ In light of similar design questions around defaults for const arguments, these For a type to be valid, in theory, as the type of a const parameter, we must be able to compare values of that type at compile-time. Furthermore, equality of values should be well-behaved (namely, it should be deterministic, reflexive, symmetric, and transitive). To guarantee these properties, the concept of *structural equality* was introduced in the [const generics RFC](https://github.com/rust-lang/rfcs/blob/master/text/2000-const-generics.md): essentially this includes any type with `#[derive(PartialEq, Eq)]` whose members also satisfy structural equality. -There are [still some questions](https://github.com/rust-lang/rust/issues/74446) concerning precisely how structural equality should behave, and [prerequisites for implementation](https://github.com/rust-lang/compiler-team/issues/323). Primitive types are significantly simpler, which has allowed use to stabilize const generics for these types before more general types. +There are [still some questions](https://github.com/rust-lang/rust/issues/74446) concerning precisely how structural equality should behave, and [prerequisites for implementation](https://github.com/rust-lang/compiler-team/issues/323). Primitive types are significantly simpler, which has allowed us to stabilize const generics for these types before more general types. ### Const generics with complex expressions