You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor(core): replace MyIterator with standard Iterator
[rust-lang/rust#106541][1] added `#[const_trait]` to `Iterator` as well
as internal attribute to bypass the constness check for other methods
than `Iterator::next`. As a result, user code can now implement `const
Iterator` in a normal way, i.e., just by implementing `Iterator::next`.
[1]: rust-lang/rust#106541
Copy file name to clipboardExpand all lines: doc/toolchain_limitations.md
+1-20Lines changed: 1 addition & 20 deletions
Original file line number
Diff line number
Diff line change
@@ -106,7 +106,7 @@ type Alias<T> = Struct<{<T as Trait>::N}>;
106
106
107
107
### `[tag:const_for]``for` loops are unusable in `const fn`
108
108
109
-
Technically it's available under the compiler feature `const_for`, but the lack of essential trait implementations (e.g., `[ref:range_const_iterator]`, `[ref:const_slice_iter]`) and above all the inability of implementing `const Iterator` (`[ref:iterator_const_default]`) make it unusable.
109
+
Technically it's available under the compiler feature `const_for`, but the lack of essential trait implementations (e.g., `[ref:range_const_iterator]`, `[ref:const_slice_iter]`) makes it unusable in many cases.
110
110
111
111
112
112
### `[tag:const_static_item_ref]``const`s and `const fn`s can't refer to `static`s
0 commit comments