Benedikt Reinartz

I'm not sure this is worth the hassle. Python's type hint system does not support (to my knowledge) multiple "full" signatures, instead one would have to fake all arguments that...

It's probably since I threw out the `dnfadmin` user. I'll check what rights it requires for the cla check.

I have disabled it for now, we will have to do the CLA checking "manually" for now, I'll check with the .NET Foundation how we can set this up without...

Indeed I have now found a way around this, check out this gist: https://gist.github.com/filmor/58f5099f96570c64b1d3 The implementation of the member access is done by basically translating the code that the C#...

My particular use case is a configuration library that allows for constructs like: ``` string proxy = c.proxy.http; ``` where `c` is a dynamic object of which the members are...

Wouldn't it make sense to instead work on getting serde_rustler in? I don't see the advantage of a custom codegen right now.

It could make sense to prefix all of the class members that we use with `clr`, like `__clr_attributes__`.

Also: @rmadsen-ks is there anything that is keeping us from just constructing the instances in Python already, like `__clr_attributes__ = [DebuggerDisplayAttribute("ExampleClrClass: X={X}")]`?

Hmm, we could theoretically special-case `System.Attribute` derivatives, or automatically introduce facades without the `Attribute` suffix (so `DebuggerDisplay("...")` which would not be a real `DebuggerDisplayAttribute` instance but just contain a reference...

Can't this be done as a separate mix plugin?