RFR: ClassicProblem_02_ProducerConsumerProblem - third try

[Michael Mirwaldt]

On Thu, 18 Nov 2021 16:38:07 GMT, Aleksey Shipilev <shade at openjdk.org> wrote:

>> This sample implements some solutions from the wikipedia article about the producer-consumer-problem on https://en.wikipedia.org/wiki/Producer%E2%80%93consumer_problem .
>> It contains these solutions:
>> - _OneProducerOneConsumer_ with semaphores
>> - _FlawedTwoProducersOneConsumer_ with semaphores in which the producers sometimes use the same index for their items and overwrite each others item in the buffer
>> - _FixedTwoProducersOneConsumer_ with semaphores which uses an extra lock for the index so that the producers never use the same index for their items
>> - _Lock_ doesn't use any sempahores but a reentrant lock with two conditions. It supports many producers and many consumers
>> - _AtomicIntegers_ neither uses any semaphores but two atomic integers and supports one producer and one consumer.
>> 
>> I have decided not to implement the last solution with finite-range single writer registers in the wikipedia article. It looked far too complicated to me.
>> 
>> This is my third try to avoid squash commits.
>
> jcstress-samples/src/main/java/org/openjdk/jcstress/samples/concurrency/classic/ClassicProblem_02_ProducerConsumerProblem.java line 250:
> 
>> 248:             lock.lock();
>> 249:             try {
>> 250:                 while(count == 0) {
> 
> The style is to leave space after `while`, `if`, `for`, etc.

IntelliJ always adds those spaces when I use the auto-format feature or any code completion feature. 
I don't put them into the samples by intention. And the default code style uses theses spaces.

Have you got a code style file for me in which your favourite code style for JCStress is defined? If so, then please send it to me via email and I will use it so that you don't need to bother such stylistic issues anymore in this PR and neither in any next PR. Ok?

-------------

PR: https://git.openjdk.java.net/jcstress/pull/104