Suggestion: FunctionOverloading

[davorm6]

For example:

function(param, x, y) {

}

function(param[], x, y) {

} 

[Y-Less]

What does:

enum A {
    B[10],
}

new a[A]

main()
{
    function(a[B], 5, 6);
}

Call?

And what about namings for public functions?

[davorm6]

The implementation of function 2 (param[])

[Y-Less]

Currently, a[B] can be passed as either an array or a cell, based on the function parameter. This would be ambiguous.

[davorm6]

Wouldn't a[B] be considered an array and a[B][0] cell?

[Y-Less]

Sometimes. Enums are somewhere between arrays and cells, they behave as both in different circumstances.

[davorm6]

How do array function parameters work 'under the hood'?

[Y-Less]

Arrays are just references (basically you pass the address of the array, they aren't a copy).

[YashasSamaga]

Some more ambiguities:

1. #emit <instruction> function
2. #if defined function
3. function(param) vs function(&param) vs function(param[]) and you call using function(arr[2])

There should be a strict set of rules which dictate how overload resolution should take place. The implementation isn't easy.

[Y-Less]

The first two could probably be resolved with the same name mangling as for public functions. But then of course existing code breaks by adding an overload:

Works fine:

public MyFunc(a)
{
}

main()
{
    #if defined MyFunc
        CallLocalFunction("MyFunc", "i", 42);
    #endif
}

Suddenly stops working:

public MyFunc(a[])
{
}

public MyFunc(a)
{
}

main()
{
    #if defined MyFunc
        CallLocalFunction("MyFunc", "i", 42);
    #endif
}

Plus, could this mask legitimate errors? Often when you define the same function twice you don't actually want to - its a typo, or copy/paste error, or you just forgot.