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
If we end up removing Seek from MemWriter as suggested in #15915, there's not much reason left to having an explicit MemWriter. Instead, we could directly implement Writer on Vec<u8>. Likewise, we could do the same with BufWriter/BufReader and &[u8] if we take advantage of the fact that neither of them return the slice, so they can shrink the slice as it is read or written to.
The text was updated successfully, but these errors were encountered:
internal: simplify the removal of dulicate workspaces.
### Summary:
Refactoring the duplicate removal process for `workspaces` in `fetch_workspaces`.
### Changes Made:
Replaced `[].iter().enumerate().skip(...).filter_map(...)` with a more concise `[i+1..].positions(...)` provided by `itertools`, which enhances clarity without changing functionality
### Impact:
This change aims to enhance the duplicate removal process for `workspaces`. This change has been tested on my machine.
Please review and provide feedback. Thanks!
If we end up removing
Seek
fromMemWriter
as suggested in #15915, there's not much reason left to having an explicitMemWriter
. Instead, we could directly implementWriter
onVec<u8>
. Likewise, we could do the same withBufWriter
/BufReader
and&[u8]
if we take advantage of the fact that neither of them return the slice, so they can shrink the slice as it is read or written to.The text was updated successfully, but these errors were encountered: