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
Currently the io-pattern needs to be passed to Sponge::start as a Vec<Call> but it would be much more convenient to have it take any type that is impl AsRef<[Call]>.
The text was updated successfully, but these errors were encountered:
With the above Sponge would need to carry a the io-pattern as a reference to slice of Call but I would prefer to have the Sponge own the io-pattern.
Solution is to give io-pattern as impl Into<Vec<Call>> as this gives the Sponge struct ownership of the io-pattern while being as unrestrictive as possible.
moCello
changed the title
Let Sponge::start take io-pattern as impl AsRef<[Call]>
Let Sponge::start take io-pattern as impl Into<Vec<Call>>Mar 8, 2024
Summary
Currently the io-pattern needs to be passed to
Sponge::start
as aVec<Call>
but it would be much more convenient to have it take any type that isimpl AsRef<[Call]>
.The text was updated successfully, but these errors were encountered: