All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Stefan Beller <sbeller@google.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	"git\@vger.kernel.org" <git@vger.kernel.org>,
	Simon Ruderich <simon@ruderich.org>, Jeff King <peff@peff.net>
Subject: Re: [PATCH] compat: Allow static initializer for pthreads on Windows
Date: Thu, 27 Oct 2016 11:49:50 -0700	[thread overview]
Message-ID: <xmqqr3716301.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <34c88c40-2088-fd74-5d26-56c0599b7eb9@kdbg.org> (Johannes Sixt's message of "Thu, 27 Oct 2016 20:22:34 +0200")

Johannes Sixt <j6t@kdbg.org> writes:

> Am 27.10.2016 um 19:01 schrieb Stefan Beller:
> ...
> It is not possible to mark a mutex uninitialized on Windows without an
> extra piece of data. A solution would become quite complicated quite
> quickly, and at the cost of additional operations that are in the same
> ballpark as an uncontended mutex. I'm not enthused.
>
>> The positive aspect of this way the patch proposes would be that any
>> future contributor not knowing the details of how to do mutexes right
>> on Windows, would not totally break the whole system, i.e. this seems
>> to be more maintainable in the future as it reduces the friction between
>> pthreads mutexes and the way we can do things in Git in a platform
>> independent way
>
> This is a non-argument. Coders have to know their tools.

The codebase should strive to give coders a coherent abstraction
that can be implemented efficiently on platforms, so that coders do
not have to care too deeply about quirks that exist on individual
platforms.

It is OK to argue that the particular solution Stefan lifted from
somewhere (perhaps msdn article he cited???) does not qualify as
such an abstraction.  But I do not agree with your "Coders have to
know" as a blanket statement.

  reply	other threads:[~2016-10-27 18:49 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26 21:57 [PATCH] compat: Allow static initializer for pthreads on Windows Stefan Beller
2016-10-26 22:14 ` Stefan Beller
2016-10-27  5:49 ` Johannes Sixt
2016-10-27  6:02   ` Junio C Hamano
2016-10-27  6:10     ` Johannes Sixt
2016-10-27  6:21       ` Junio C Hamano
2016-10-27  6:29         ` Johannes Sixt
2016-10-27  6:33         ` Junio C Hamano
2016-10-27 17:01           ` Stefan Beller
2016-10-27 17:11             ` Jeff King
2016-10-27 18:22             ` Johannes Sixt
2016-10-27 18:49               ` Junio C Hamano [this message]
2016-10-27 19:08                 ` Stefan Beller
2016-10-27 20:05                   ` Johannes Sixt
2016-10-27 21:49                     ` Jacob Keller
2016-10-27 21:59                       ` Stefan Beller
2016-10-28  5:55                       ` Johannes Sixt
2016-10-28  6:11                         ` Jacob Keller
2016-10-28 13:01                         ` Philip Oakley
2016-10-28 18:49                           ` Jacob Keller
2016-10-28 11:58                       ` Johannes Schindelin
2016-10-28 18:48                         ` Jacob Keller
2016-10-28 20:26                           ` Johannes Sixt
2016-10-28 20:29                             ` Junio C Hamano
2016-10-28 20:36                               ` Stefan Beller
2016-10-28 20:38                                 ` Junio C Hamano
2016-10-28 20:49                               ` Johannes Sixt
2016-10-28 20:52                                 ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqr3716301.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.org \
    --cc=peff@peff.net \
    --cc=sbeller@google.com \
    --cc=simon@ruderich.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.