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
Hi, wouldnt there be a problem with function purity? Iterator::next is pure but unless the StorageVec would be preloaded as VecIter the next would require some reads. Asking out of curiosity :)
So implementation that would look like this is not feasible unless there would be a new Iterator trait for Storage structs:
An internal contributor has requested the
Iter
trait be implemented forStorageVec
The text was updated successfully, but these errors were encountered: