Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Your question is ironic. You're wondering why the Java community is struggling with three different proposals for adding closures, and your suggested solution is to add a fourth option to the mix?</p> <p>But to answer your question:</p> <ul> <li><p>The right forum for discussion is the mailing list of openjdk project lambda. This is not a place where suggestions are likely to influence that effort.</p></li> <li><p>The type systems for C# and Java are significantly different, so the C# solution would not directly apply. For example, C# has declaration-site variance (in/out), while java has use-site variance (wildcards). Inference of lambda parameter types as specified in C# would not apply in Java.</p></li> <li><p>The evolution of Java must remain backward compatible, but adding the delegate keyword would be a breaking change.</p></li> <li><p>C# has three types of delegate expressions: the old one with the delegate keyword, statement lambdas with =>{, and expression lambdas. If the C# language team has it to do over again, we'd certainly not have this many forms. Why should Java adopt C#'s historical baggage?</p></li> <li><p>Because C# generics operate over primitives, the Func&lt;> and Action&lt;> delegate types can be used as poor-man's structural function types. But in Java, generics are erased, work only over reference types, and types cannot be distinguished by their arity. Consequently Java would have to have a large number of distinctly-named "standard" function types to get the same effect. That would not be pretty.</p></li> </ul> <p>Overall, the C# solution does not adapt to a very natural solution in Java.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhy not .NET-style delegates rather than closures in Java?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDónal
    1. USNeal Gafter
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COJust curious about the line "If the C# language team has it to do over again, we'd certainly not have this many forms." - was that a quote from the C# team, or just your take on the somewhat redundant statement lambda and delegate syntaxes?
      singulars
      1. PO
      1. USBittercoder
    2. COFYI: I am on the C# language team. Given that we will not have it to do over again, it would be meaningless to give any official status to my opinion. But my point is that the "delegate" form of lambda expression has in practice been replaced by the "=>" form.
      singulars
      1. PO
      1. USNeal Gafter
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload