Mailing-List: contact dev-help@river.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@river.apache.org
Received-SPF: pass (nike.apache.org: domain of grahnian@gmail.com designates
 209.85.161.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=Jp16sqKeZ9igAGnrCHD7Gwz3tF7y2pQ/+hGuf8Px3Cd+awqc5+IyH9DYd6F72kIf/r
         DBFnI8tfHwh/2yx6NzJiaD2l3Oc1xFAjH9Tp4hkz2KjNV6q5FcGwquqnrOFjaH1PYbTc
         qwwHH6H5+tgRYbZ+wOWbOJemao/aJrleEgrKQ=
MIME-Version: 1.0
In-Reply-To: <BANLkTimtBhy_P7T7PoCsYywn1ZAfewuTrA@mail.gmail.com>
References: <BANLkTimfsv_jSSYsK8+PV-_FQdFCOb9trg@mail.gmail.com>
	<DE2C5331EF5E0646B3E4687750E3A9F8515E0CDD94@IE2RD2XVS041.red002.local>
	<BANLkTi=7y40XNDiJDt0vk=gQmfi_Skkt+A@mail.gmail.com>
	<4DE6E51F.1020409@zeus.net.au>
	<4DE6ECAC.6070104@acm.org>
	<4DE6F582.7010904@zeus.net.au>
	<4DE70494.7000100@zeus.net.au>
	<BANLkTimzua-McArTV7YgvS=GYxvu8dE4Qg@mail.gmail.com>
	<4DE7368F.4080308@zeus.net.au>
	<BANLkTi=L87MDsaUpA-Q=ap5RErYigPc2DA@mail.gmail.com>
	<BANLkTimtBhy_P7T7PoCsYywn1ZAfewuTrA@mail.gmail.com>
Date: Thu, 2 Jun 2011 12:39:23 -0400
Message-ID: <BANLkTinxFJ047PrtX7AvWcL1KVnXcjp8Jw@mail.gmail.com>
Subject: Re: correctness, generics, and spaces
From: James Grahn <grahnian@gmail.com>
To: dev@river.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jun 2, 2011 at 11:58 AM, Dan Creswell <dan.creswell@gmail.com> wrote:
> I recall one of the reasons for introducing generics was because force
> of sufficient reasoning proved ineffective such that people would get
> runtime casting problems when extracting objects from collections.

I find the comparison apt: the choice is making a correct cast in a
central location vs. having everyone manually cast.

> Regardless we can have an endless debate about this or do some
> practical experimentation. So....

We do have a platform for practical experimentation already.   The
generics branch of the code has the bulk of what's under discussion,
though it needs a small patch to eliminate a corner case (again,
coming soon).

That branch, however, mutates the existing interfaces and classes.
If we wish to present both interfaces as options to users, that will
have to be changed.   Which is entirely doable, if that's the
consensus for a next step.

jamesG