It has similar "source generator" hallmarks like in OP's post, for example calling a generic constructor which is JITted to a deeply nested struct type.
It's (in my opinion) very hard to reason what the code is doing because it has that flavor of "writing code to generate source to generate code"
It's impressive. And i'm pretty sure it's only real hinderance, why it could not be adopted into the base library, is that the repo needs a phd holder to finish implementing the `IList` interface because deleting is really difficult and theoretical.
https://github.com/julesjacobs/ImmutableCollections/discussi...
It has similar "source generator" hallmarks like in OP's post, for example calling a generic constructor which is JITted to a deeply nested struct type.
It's (in my opinion) very hard to reason what the code is doing because it has that flavor of "writing code to generate source to generate code"
It's impressive. And i'm pretty sure it's only real hinderance, why it could not be adopted into the base library, is that the repo needs a phd holder to finish implementing the `IList` interface because deleting is really difficult and theoretical.