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
Purpose of code changes on this branch:
Rev 125: Implementation of the RunLengthEncode() extension method which
operates on sequences and produces a new sequence representing the
occurrence of repeated runs of the same value in the original. The
resulting (transformed) sequence consists of zero or more
KeyValuePair<T,int> elements - where the Key identifies the item and the
Value is the occurrence count of that item in the original sequence.
RunLengthEncode has an overload that allows the caller to supply equality
semantics for the elements of the sequence being transformed.
RunLengthEncode is intended to operate in a deferred, streaming fashion -
allowing it to process sequences of arbitrary (or infinite) length.
When reviewing my code changes, please focus on:
* The public interface of the extension method.
* The effectiveness and clarity of the available XML comment documentation.
* How well this operator fits into the MoreLINQ ecosystem of
extension methods.
* The extent of coverage available from the corresponding unit tests.
* Whether edge cases are correctly identified and handled in the
implementation and tests.
* Whether the operator adheres to the description and behavior described above.
After the review, I'll merge this branch into:
/trunk
Original issue reported on code.google.com by ambientl...@gmail.com on 18 Jan 2010 at 3:14
The text was updated successfully, but these errors were encountered:
Now migrated to Hg and available in clone:
http://code.google.com/r/azizatif-morelinq-evenmore/
This clone is ready to be cloned :O) for further review. It also has the
main/default branch already merged in to bring it up to date.
Original comment by azizatif on 25 May 2012 at 11:38
Following no response from ambientlion (who possibly/assuming lost interest
given it has taken years to get this far), taking ownership of issue to
consider as addition for MoreLINQ 2.0 milestone.
Original comment by azizatif on 12 Jun 2013 at 10:10
Original issue reported on code.google.com by
ambientl...@gmail.com
on 18 Jan 2010 at 3:14The text was updated successfully, but these errors were encountered: