Home/ Questions/Q 5935219
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T15:13:23+00:00

In this video from Google IO 2009 , the presenter very quickly says that

  • 0

In this video from Google IO 2009, the presenter very quickly says that signatures of methods should return concrete types instead of interfaces.

From what I heard in the video, this has something to do with the GWT Java-to-Javascript compiler.

  • What’s the reason behind this choice ?
  • What does the interface in the method signature do to the compiler ?
  • What methods can return interfaces instead of concrete types, and which are better off returning concrete instances ?

Snippet of code from Google IO presentation showing it's better that your method returns ArrayList than List

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This has to do with the gwt-compiler, as you say correctly. EDIT: However, as Daniel noted in a comment below, this does not apply to the gwt-compiler in general but only when using GWT-RPC.

    If you declare List instead of ArrayList as the return type, the gwt-compiler will include the complete List-hierarchy (i.e. all types implementing List) in your compiled code. If you use ArrayList, the compiler will only need to include the ArrayList hierarchy (i.e. all types implementing ArrayList — which usually is just ArrayList itself). Using an interface instead of a concrete class you will pay a penalty in terms of compile time and in the size of your generated code (and thus the amount of code each user has to download when running your app).

    You were also asking for the reason: If you use the interface (instead of a concrete class) the compiler does not know at compile time which implementations of these interfaces are going to be used. Thus, it includes all possible implementations.

    Regarding your last question: all methods CAN be declared to return interface (that is what you ment, right?). However, the above penalty applies.

    And by the way: As I understand it, this problem is not restricted to methods. It applies to all type declarations: variables, parameters. Whenever you use an interface to declare something, the compiler will include the complete hierarchy of sub-interfaces and implementing classes. (So obviously if you declare your own interface with only one or two implementing classes then you are not incurring a big penalty. That is how I use interfaces in GWT.)

    In short: use concrete classes whenever possible.

    (Small suggestion: it would help if you gave the time stamp when you refer to a video.)

    • 0