>> align with the project's whitespace specs
I’ve been trying to find the project’s code formatting document, but was unsuccessful.
>> Second, assuming we have no threading issues at the moment, how can we be sure this doesn't introduce any?
We can be sure of nothing, since certainty is only as strong as the assumptions it is based on.
- the tests have been appropriately changed and use the new code, and they all pass.
- On a more personal level (even though it means nothing since you have to take my unverifiable word for it), this code has been in production use these past 3 months on a 28-core machine, all of them writing to a single IndexWriter for about a hundred million documents, repeatedly. No problems were ever seen.
These things don’t show the absence of problems, but make me reasonably confident that the code is sound.
From: Itamar Syn-Hershko [mailto:firstname.lastname@example.org]
Sent: Tuesday, June 13, 2017 9:09 AM
To: apache/lucenenet <email@example.com>
Cc: Van Den Berghe, Vincent <Vincent.VanDenBerghe@bvdinfo.com>; Author <firstname.lastname@example.org>
Subject: Re: [apache/lucenenet] LUCENE-5644: switch to simpler LIFO thread to ThreadState allocator d… (#208)
Thanks, that's an interesting one.
First, there's a lot of whitespace noise - can you remove it please? (align with the project's whitespace specs)
Second, assuming we have no threading issues at the moment, how can we be sure this doesn't introduce any? cc @NightOwl888