| Andrew Cooke | Contents | Latest | RSS | Twitter | Previous | Next

C[omp]ute

Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Lepl parser for Python.

Colorless Green.

Photography around Santiago.

SVG experiment.

Professional Portfolio

Calibration of seismometers.

Data access via web services.

Cache rewrite.

Extending OpenSSH.

C-ORM: docs, API.

Last 100 entries

Lepton Decay Irregularity; An Easier Way; Julia's BinDeps (aka How To Install Cairo); Good Example Of Good Police Work (And Anonymity Being Hard); Best Santiago Burgers; Also; Michael Emmerich (Vibrator Translator) Interview (Japanese Books); Clarice Lispector (Brazillian Writer); Books On Evolution; Looks like Ara (Modular Phone) is dead; Index - Translations From Chile; More Emotion in Chilean Wines; Week 7; Aeon Magazine (Science-ish); QM, Deutsch, Constructor Theory; Interesting Talk Transcripts; Interesting Suggestion Of Election Fraud; "Hard" Books; Articles or Papers on depolarizing the US; Textbook for "QM as complex probabilities"; SFO Get Libor Trader (14 years); Why Are There Still So Many Jobs?; Navier Stokes Incomplete; More on Benford; FBI Claimed Vandalism; Architectural Tessellation; Also: Go, Blake's 7; Delusions of Gender (book); Crypto AG DID work with NSA / GCHQ; UNUMS (Universal Number Format); MOOCs (Massive Open Online Courses); Interesting Looking Game; Euler's Theorem for Polynomials; Weeks 3-6; Reddit Comment; Differential Cryptanalysis For Dummies; Japanese Graphic Design; Books To Be Re-Read; And Today I Learned Bugs Need Clear Examples; Factoring a 67 bit prime in your head; Islamic Geometric Art; Useful Julia Backtraces from Tasks; Nothing, however, is lost with less discomfort than that which, when lost, cannot be missed; Article on Didion; Cost of Living by City; British Slavery; Derrida on Metaphor; African SciFi; Traits in Julia; Alternative Japanese Lit; Pulic Key as Address (Snow); Why Information Grows; The Blindness Of The Chilean Elite; Some Victoriagate Links; This Is Why I Left StackOverflow; New TLS Implementation; Maths for Physicists; How I Am 8; 1000 Word Philosophy; Cyberpunk Reading List; Detailed Discussion of Message Dispatch in ParserCombinator Library for Julia; FizzBuzz in Julia w Dependent Types; kokko - Design Shop in Osaka; Summary of Greece, Currently; LLVM and GPUs; See Also; Schoolgirl Groyps (Maths); Japanese Lit; Another Example - Modular Arithmetic; Music from United; Python 2 and 3 compatible alternative.; Read Agatha Christie for the Plot; A Constructive Look at TempleOS; Music Thread w Many Recommendations; Fixed Version; A Useful Julia Macro To Define Equality And Hash; k3b cdrom access, OpenSuse 13.1; Week 2; From outside, the UK looks less than stellar; Huge Fonts in VirtualBox; Keen - Complex Emergencies; The Fallen of World War II; Some Spanish Fiction; Calling C From Fortran 95; Bjork DJ Set; Z3 Example With Python; Week 1; Useful Guide To Starting With IJulia; UK Election + Media; Review: Reinventing Organizations; Inline Assembly With Julia / LLVM; Against the definition of types; Dumb Crypto Paper; The Search For Quasi-Periodicity...; Is There An Alternative To Processing?; CARDIAC (CARDboard Illustrative Aid to Computation); The Bolivian Case Against Chile At The Hague; Clear, Cogent Economic Arguments For Immigration; A Program To Say If I Am Working; Decent Cards For Ill People; New Photo

© 2006-2015 Andrew Cooke (site) / post authors (content).

Using a New Scope to Avoid Type Capture with Java Generics

From: "andrew cooke" <andrew@...>

Date: Tue, 9 Sep 2008 08:25:18 -0400 (CLT)

This is a little trick for Java Generics that's worth knowing.  It's
mentioned very briefly in Wadler's book (p27-8), but you could easily miss
it.

The problem happens when you are dealing with type parameters that you
know are consistent, but which are not explicit in your code.  This is
common if you are processing a not-completely-typed collection.

To make things clearer, I'll use the following example:  Consider a system
that transfers various values from one place to another (perhaps it is a
scheduler sending messages of different types within a system).

We might have an interface that can both provide and receive certain
message types:

public interface Connection<Type>
{
  Type read();
  void write(Type value);
}

And our scheduler might look something like this:

class Scheduler
{
  public void process(Collection<Connection<?>> cnxs)
  {
    for (Connection<?> cns: cnxs) {
      cnx.write(cnx.read);
    }
  }
}

(Note that <?> is shorthand for <? extends Object> and we use it here
because the cnxs collection contains a Connections with a variety of
different type parameters).

Unfortunately that won't compile!  The error given be Eclipse with Java
1.6 is "The method write(capture#2-of ?) in the type
Connection<capture#2-of ?> is not applicable for the arguments
(capture#3-of ?)".

The reason this won't compile is that the type parameter for the value
being returned by the Connection and the type parameter for the value it
will receive are being treated separately.  Each is being treated as
"capture-of ?" which means "some subclass of Object".  And the compiler is
then (understandably) saying "I can't send 'subclass X of Object' to a
method that expects 'subclass Y of Object' because I don't know if they
are the same subclass".

To make this work we need to introduce the common type parameter
explicitly.  Unfortunately the following code, or something like it,
doesn't work (as far as I can tell).  There is no way to introduce a type
parameter in the middle of a block of code (what we really want here is
better support for polymorphism):

class Scheduler
{
  public void process(Collection<Connection<?>> cnxs)
  {
    // syntax error!
    for (<E> Connection<E> cns: cnxs) {
      E value = cnx.read();
      cnx.write(value);
    }
  }
}

But what we can do is add a helper method that introduces a new type
parameter:

class Scheduler
{
  public void process(Collection<Connection<?>> cnxs)
  {
    for (Connection<?> cnx: cnxs) {
      helper(cnx);
    }
  }
  private <E> void helper(Connection<E> cnx)
  {
    E value = cnx.read();
    cnx.write(value);
  }
}

This does what we want!  The code validates, compiles, and runs.

In summary then:  Sometimes you can "lose" an explicit generic type
parameter (often because you are dealing with a collection of different
types).  You can re-introduce that type parameter by adding an extra
helper method.

Andrew

Comment on this post