Explore the option to implement automatic conversion of primitive numeric types to their counterpart reference types

[slavchev]

byte -> java.lang.Byte
short -> java.lang.Short
int -> java.lang.Integer
long -> java.lang.Long
float -> java.lang.Float
double -> java.lang.Double

Module team found this issue in the following example:

function createReminder()
{
    var beginTime = java.util.Calendar.getInstance();
    beginTime.set(2012, 9, 14, 7, 30);
    var startMillis = beginTime.getTimeInMillis();
    var values = new android.content.ContentValues();
    // !!!
    values.put(android.provider.CalendarContract.Events.DTSTART, startMillis);
}

Workaround: for example long -> java.lang.Long.valueOf(...)

[Plamen5kov]

We decided it's best to force the user to explicitly use the specific data type, because the runtime will sometimes be unable to figure out what conversion to make.
Example:
method put of android.content.ContentValues takes parameters float and double. In this case the user has to specify what overload he wants to use.