-
-
Notifications
You must be signed in to change notification settings - Fork 852
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rewrite ChunkedMemoryStream #2828
Merged
+405
−432
Merged
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
1e58db2
Remove ChunkedMemoryStream
JimBobSquarePants 1a15078
Update BufferedStreams.cs
JimBobSquarePants ee53532
Merge branch 'release/3.1.x' into js/issue-2806
JimBobSquarePants c418bb0
Revert "Remove ChunkedMemoryStream"
JimBobSquarePants 48645f8
Rewrite ChunkedMemoryStream
JimBobSquarePants f96f8ca
Revert "Update BufferedStreams.cs"
JimBobSquarePants 03343c4
Simplify and optimize position checking
JimBobSquarePants b74d2e4
Add WriteByte and optimize ReadByte
JimBobSquarePants 6301662
Feedback updates and massively expand write tests
JimBobSquarePants c45702d
Fix read bug.
JimBobSquarePants c4fd666
Update tests/ImageSharp.Tests/IO/ChunkedMemoryStreamTests.cs
JimBobSquarePants File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Feedback updates and massively expand write tests
- Loading branch information
commit 630166211c7c3d1b6b56f250bf198cc967d3e42b
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sidenote: IMO it's fairly conventional in C# land to prefix private field names with an underscore, to allow easy distinction from local variables, and to avoid excessive use of
this.
. I assume this is your personal preference, but thought I'd mention it as IMO it is somewhat non-idiomatic C#.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, but I'd rather stick to using the language as designed rather than using conventions carried over from C.
The
this
keyword provides important context IMO and encouraged consistancy throughout a codebase.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@colgreen the project's preferred coding style is based on Framework design guidelines, and on StyleCop recommendations. The guidelines explicitly prohibit prefixing variables.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The guidelines state
Internal and private fields are not covered by guidelines,
(I believe those guidelines are primarily related to public API surface, rather than private/internal naming). The underscore prefix for private fields is very common in my experience, e.g. it's used widely in Microsoft .NET repos.However, this topic is probably not relevant in the context of this PR :)