Friedrich von Never

I think that in theory also for Mono, but why are you asking?

I agree on that point. Any ideas how such a function could work? The problem is that sometimes it's hard to distinguish a vararg function from the call-site point of...

> I think we can pass variadic arguments as `object[]` and that's it. To be honest, I'm not sure we can put a pointer into an `object[]`. Is a pointer...

What does the standard say about this? I'm not sure these signatures are technically compatible.

Well, I'd say we want something that will reliably work on all the supported platforms and runtimes.

I do not like the solution involving any such hacks. Remember that we have to support at least 9 OS/CPU combinations (x86/x64/ARM64 macOS/Win/Lin). I do not believe there's a reliable...

I'd say it already costs us a lot of resources in proper support. Maybe we can implement some easy workaround instead, like ignoring the argument lists for these functions completely...

Could you please clarify the question? What exactly are you looking for? Currently, this exact definition (`foo_t v = foo`) doesn't work. I'd suggest starting looking from this place: https://github.com/ForNeVeR/Cesium/blob/720b4cbb3f218d535f059d8ca7df28f3392b4057/Cesium.CodeGen/Ir/Expressions/Values/FunctionValue.cs#L21-L24

Ok, after some thought, I've decided we'll try to support the following architecture sets in Cesium: - `32b`: an architecture with 32-bit pointers, gets compiled as an x86 assembly (maybe...

Seems like `wide` will require a separate version of the standard library. We could either compile it using `#if` magic, or have fun with Cecil and post-processing.