public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Janus Weil <janus@gcc.gnu.org>
To: gfortran <fortran@gcc.gnu.org>
Subject: Re: Poll on short circuiting
Date: Wed, 01 Aug 2018 20:37:00 -0000	[thread overview]
Message-ID: <CAKwh3qgp-LNG61DBTaS_Pz57=KbOnH+5Pb3tvPEofc7aZbe0pg@mail.gmail.com> (raw)
In-Reply-To: <CAKwh3qhP1WPXGE1oThGi-i7Akqv8Ah9xDw+dEPu_AoCXHd4fmA@mail.gmail.com>

Thanks to everyone who participated so far. At this point it seems
that the results reflect the controversy of the debate we had.

Note that I just edited the entries of those people who chose the
"always" option, checking all those boxes which are implied by
"always" (so that the poll is easier to read vertically). In hindsight
I should probably have left out the options "always" and "never",
which are representable by combinations of the other options.

Since there are no really clear majorities, I guess we don't really
learn a lot from this so far, except for some rather points:
* Everyone wants to do short-circuiting in some form (no one chose "never").
* The people who don't care didn't participate.
* Almost everyone wants to do short-circuiting with pure functions.

However, it seems many gfortran contributors have not participated
yet. I hope some people will still do it.

Cheers,
Janus



2018-07-30 23:00 GMT+02:00 Janus Weil <janus@gcc.gnu.org>:
> Dear gfortran community,
>
> since our recent discussions on short-circuiting did not really come
> to a conclusive end (and we mostly just heard two loud minorities up
> to now), I thought it would be nice to hear what the silent majority
> thinks. Therefore I opened a quick doodle poll on this topic:
>
> https://doodle.com/poll/gisivemyrpnkqnpm
>
> I'd like to invite everyone who has an opinion on this to share it
> with us, no matter if you're a contributor or a user of gfortran.
> Plenty of arguments have been made for all the different options, see
> the references below.
>
> I'm not sure if this will be helpful at all, but I think it's worth a
> try. We'll see what comes out ...
>
> Cheers,
> Janus
>
>
>
> References:
> [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57160
> [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
> [3] https://gcc.gnu.org/ml/fortran/2018-06/msg00065.html (plus follow-ups)
> [4] https://gcc.gnu.org/ml/fortran/2018-07/msg00017.html (plus follow-ups)
> [5] https://gcc.gnu.org/ml/fortran/2018-07/msg00086.html (plus follow-ups)
> [6] some never-ending c.l.f. discussions

  reply	other threads:[~2018-08-01 20:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30 21:00 Janus Weil
2018-08-01 20:37 ` Janus Weil [this message]
2018-08-06 20:51   ` Janus Weil

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='CAKwh3qgp-LNG61DBTaS_Pz57=KbOnH+5Pb3tvPEofc7aZbe0pg@mail.gmail.com' \
    --to=janus@gcc.gnu.org \
    --cc=fortran@gcc.gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).