caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David MENTRE <dmentre@linux-france.org>
To: "José Romildo Malaquias" <j.romildo@gmail.com>,
	"caml users" <caml-list@inria.fr>
Subject: Re: [Caml-list] Accessing record fields
Date: Mon, 16 Sep 2013 09:52:27 +0200	[thread overview]
Message-ID: <CAC3Lx=YDaeGAuFqxZw=U1aASiQ+hwuFP=OmexbCk4t+apr2vvA@mail.gmail.com> (raw)
In-Reply-To: <20130915103027.GA21344@jrm>

Hello,

2013/9/15 José Romildo Malaquias <j.romildo@gmail.com>:
> Which one would be preferred in this case: f or g?

Use the one which is the more readable and maintainable in the long
term, especially for micro-optimization like this.

Best regard,
david

      parent reply	other threads:[~2013-09-16  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-15 10:30 José Romildo Malaquias
2013-09-15 10:38 ` Jacques-Henri Jourdan
2013-09-16  7:37   ` Goswin von Brederlow
2013-09-16  7:52 ` David MENTRE [this message]

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='CAC3Lx=YDaeGAuFqxZw=U1aASiQ+hwuFP=OmexbCk4t+apr2vvA@mail.gmail.com' \
    --to=dmentre@linux-france.org \
    --cc=caml-list@inria.fr \
    --cc=j.romildo@gmail.com \
    /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 NNTP newsgroup(s).