Igor Bagdamyan

I don't really like it from first glance. It seems to introduce a huge change in F# making loops actually return something other than "unit" but it seems to support...

@cartermp any change of redesining type inference to pick up best match (like int in this case) or is to too breaking?

@dsyme @KevinRansom Is there any progress on this? This (with @abelbraaksma 's fixes) would actually be useful in compiler internals. There are places where List.chooce could be easily replaced with...

It is not a bug. It's a difference between "value" and "function". Your first example assigns a "function object / delegate" to a field (I'm assuming you're doing this inside...

Techinally a function in a module is a static method in a static class while fsharpfunc is a dedicated type. This can create friction as there ateibutes that have strict...

Related: https://github.com/m4rs-mt/ILGPU/issues/1209

@m4rs-mt Some build failures are related to .Net 6 runtime not having support for `ref field`. .Net 6 is out of support currently. Do you think ILGpu should support it...

@jaredpar I wonder if there is some document describing your view of the C# lifetime system with goals, imaginary syntax and so on? I'm really curious how you envision such...

@jaredpar Yes, explicit lifetime annotations in C#. How they would work with IDisposable, would they work with reference types, pointers? What would be design goals: is it to enhance ref...

@jaredpar Yes, explicit lifetime annotations in C#. How they would work with IDisposable, would they work with reference types, pointers? What would be design goals: is it to enhance ref...