<--- Didn't read the first section of this PR

I think as a useful median between first class functions, functions names/signatures should be able to be overwritten. That shouldn't be a problem in a future where you could do Function = function(Args)[Type]{...}, Function = function(SameArgTypes)[SameType]{...}.

# library.txt
function void table:myLibraryFunc() {
    error("This is a stub! Define it in your code!")
}

.........
# file.txt
#include library.txt

function void table:myLibraryFunc() {
    print(This)
}

e.g., I wanted to create a library in E2 that works best with function references but to do so would require disabling @strict with this change, which isn't ideal, so my idea was to instead have it call one function that the user implements. I guess I could also simply not define it but it'll produces errors everywhere in the library.

<--- Didn't read the first section of this PR

I think as a useful median between first class functions, functions names/signatures should be able to be overwritten. That shouldn't be a problem in a future where you could do Function = function(Args)[Type]{...}, Function = function(SameArgTypes)[SameType]{...}.

# library.txt
function void table:myLibraryFunc() {
    error("This is a stub! Define it in your code!")
}

.........
# file.txt
#include library.txt

function void table:myLibraryFunc() {
    print(This)
}

e.g., I wanted to create a library in E2 that works best with function references but to do so would require disabling @strict with this change, which isn't ideal, so my idea was to instead have it call one function that the user implements. I guess I could also simply not define it but it'll produces errors everywhere in the library.

Either the library should define table:myLibraryFunc() or the function should be taken as a callback to another function.

Either the library should define table:myLibraryFunc() or the function should be taken as a callback to another function.

Actually, maybe a better solution, if you could add UDFs to #ifdef then this could be mitigated without adding overriding.

Either the library should define table:myLibraryFunc() or the function should be taken as a callback to another function.

Actually, maybe a better solution, if you could add UDFs to #ifdef then this could be mitigated without adding overriding.

Yeah, which would require removing overriding / "runtime" functions. I'm ofc open to that even if I think #ifdef should probably be scrapped in favor of a more general #if in the future

Should be merged after #2829 for the people currently using stringcalls and @strict for whatever reason