HdrHistogram
A fix for HistogramBase.AllValues() returning a repeat of the last HistogramIterationValue
I found that HistogramBase.AllValues() was returning an IEnumerable that contained the same HistogramIterationValue, which was the value of the last bucket in the histogram. This PR contains a test and a fix for this problem.
Additionally, I also had some trouble building the project and running the tests on an out-of-the-box VS2017, so did some work to make that happen.
:white_check_mark: Build HdrHistogram.NET 2.7.0-ibjxfkkf completed (commit https://github.com/HdrHistogram/HdrHistogram.NET/commit/27c87e615f by @)
:white_check_mark: Build HdrHistogram.NET 2.7.0-ibjxfkkf completed (commit https://github.com/HdrHistogram/HdrHistogram.NET/commit/27c87e615f by @)
Thanks for the PR @mtikilay I am busy in a conference at the moment, but will look at this ASAP.
Thanks @mtikilay for your support. Help from the community makes Open Source work! You may see I have made notes against the code changes, but maybe I can summarise here.
1 Mutable Enumerated Values
I think that maybe keeping the port of the Java mutable value is not useful. You have proved that it is non-intuitive, and arguably(?) not idiomatic IEnumerable pattern. I am happy to look at PR that tackles this in isolation. See new issue #65
2 Unit tests
I am happy to make some changes if running unit tests isn't working in VS out of the box. However, it must keep the existing tests and benchmarks working. It is clear that the documentation/readme is lacking on how to run the unit tests and benchmarks. See new issue #66
3 Test and benchmark versions
This is a library, so I want to keep the broadest scope available to my clients. I believe but could be wrong, that currently the best way to do this is to target ".NET 4.7" and "netcoreapp1.1". However, I just realised, that it doesn't prevent us from using higher versions for our tests and benchmarks. Infact, for our benchmarks this is probably favourable.
4 Ideally one PR changes one thing
Maybe I am just being a stick in the mud, but I kinda prefer that if we get a PR that is solves on thing, and solves it really well e.g. Mutable Enumerated Values #65. Also it is nice if you create the issue first, so it isn't too much of a surprise to the maintainer when the PR comes in. This give us both a channel to discuss the change. Keeping the PRs tight and specific also allows me to take bits of your work, without having reject all of it some of it isn't ideal.
Are you keen to help me out with #65 and #66?
Hi @LeeCampbell -- thanks for your detailed reply. Apologies for taking a while to get back to you. First of all, yes, let's scrap this PR and I'll do this properly in two separate ones that address just the issues in question. I agree that one PR per one thing is definitely the right approach.
So apologies for a sloppy PR and the mashing of framework version numbers and so on -- I was just trying to build the project on a vanilla VS2017 setup and it wasn't happy out of the box for some reason. I'll drop those bits from the actual commit, but it would definitely be good to have the project painlessly build and run on a standard install of the current Visual Studio. Regarding the how-to on running tests, your line is perfectly fine. I'm just not yet familiar with the standard ways of setting up and running tests projects in the .Net Core world.
As for the actual reason I put the PR in, namely the issue of the mutating .Current and the odd result of AllValues().ToList(), I think that yes, the expectation of an average .Net dev (e.g. me!) would be that you wouldn't have to iterate and copy iterator.Current yourself. I do understand your concerns regarding allocation but this should probably be either clearly signposted with documentation and more descriptive method names, or behave like other IEnumerables people are used to... Perhaps try to keep both approaches: expose IEnumerator-returning methods as they are and just enforce cloning in those HistogramBase methods that return IEnumerables? I'll see if I can make that look nice.
Also, using .MemberwiseClone does feel a bit dirty -- I'll change it to explicit object creation to make clear what is happening.
I'll try to get this done in the next couple of weeks.
Cheers, MT