var foo = new ISomeInterface {  // <-- Interface, not class
  public void ImplementInterface(int something) {
    // blah blah blah
  }

  public void AnotherInterfaceMethod(string s) {
    // ...
  }
}

• unsigned integers as a type (Integer.fooUnsigned is kind of ugly), particular bytes.
• value types.
• operator overloading.
• generics that are actually generics. Type erasure sucks.

• correct arithmetic. Seriously. How the hell can they get away with this nonsense[^]?

harold aptroot wrote:

unsigned integers as a type (Integer.fooUnsigned is kind of ugly), particular bytes.

harold aptroot wrote:

value types.

operator overloading.

harold aptroot wrote:

generics that are actually generics. Type erasure sucks.

harold aptroot wrote:

correct arithmetic. Seriously. How the hell can they get away with this nonsense[^]?

Integer[] arrayOfStuff = functionThatReturnsAnArray();
Iterable<Integer> iter = arrayOfStuff;

Integer[] arrayOfStuff = {1, 2, 3, 4};
Iterable<Integer> iter =  Arrays.asList(arrayOfStuff);

cough cough

Ian Shlasko wrote:

Property syntax...

"Wildcard arguments for generics. If I have Foobar<int> and Foobar<String>, it's nice to be able to put them in a collection/array typed as Foobar<?>. The '? extends X' and '? super X' syntax might be a bit much, though."

C-P-User-3 wrote:

Is it possible to get a living human at Skype who speaks the customer's native language in a dialect which is common to the native inhabitants of the customer's own country ?

C-P-User-3 wrote:

No joke ! Same thing happened here.