Update outdated `const` context message

This commit is contained in:
Esteban Kuber 2024-09-23 17:41:41 -07:00 committed by GitHub
parent 318f5e60e9
commit 3148a9f9a6
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 3 deletions

View File

@ -1036,9 +1036,8 @@ There are many reasons for this restriction:
is total than it is to ensure that it is deterministic; thus, while
it is regrettable, this is an acceptable trade-off.
+ Finally, note that `const fn`s, when coupled with planned future extensions,
can become quite expressive. For example, it is already planned that `loop`s,
`match`es, `let` statements, and `panic!(..)`s will be allowed.
+ Finally, note that `const fn`s, can become quite expressive. For example,
it is possible to use `loop`s, `match`es, `let` statements, and `panic!(..)`s.
Another feasible extension in the future is allocation.
Therefore, constant expressions should be enough to satisfy most expressive