Ok, that was a pain in the ass. Apparently EVERYTHING is a method when you get down to the ISymbol level. Getters and setters, event handlers, even constructors.

I don't know if I should praise or damn you for forcing me to learn so much more about Roslyn.

I posted version 0.10.0 up on NuGet. Let me know how it works.

Thank your for you fast implementation! Hope i can stay on the praise side of things :)

I tested boldly with MemoryStream:

using Tortuga.Shipwright;

namespace Traits.Examples;

[UseTrait(typeof(MemoryStream), AutoExpose = Expose.All)]
public partial class StreamComposition
{
    public StreamComposition()
    {
    }
}

And have found two issues:

1. The out keyword is not transferred for TryGetBuffer(out ArraySegment<byte> buffer)
2. A function wrapper for protected override void Dispose(bool disposing) of MemoryStream is generated. Seems like the access modifier is not taken into account. After that the Dispose() of Stream is not used for the wrapper. Additional, I would not be able to extend the dispose behavior since the original Dispose() of Stream is not virtual. Exactly a problem which is solved by [Expose] I guess since it would allow me to manually implement it.

Both issues lead to a compilation error in generated class.

However, for my current needs I am more happy with what I got.
Still wanted to give some feedback for your kind effort.

THX again 👍

That makes sense because we assume the person putting on the [Expose] attribute is checking the visibility.

So I think we can fix this by setting it to only auto-expose public methods.

P.S. Feedback helps a lot to keep me motivated.

So I think we can fix this by setting it to only auto-expose public methods.

That makes sense to me. And since I am interested in composition I am not supposed to fiddle around with anything that is protected. At least for that use-case.

One way out of the "Dispose()-Issue" could be something like [ExcludeAutoExpose(nameof(Stream.Dispose()))]. This way an implementation could be done manually, taking into account all Traits that need disposing.
Smells like the diamond problem. Going down a rabbit hole...

I just dropped 0.11.0 with support for MemoryStream's output parameters.

One way out of the "Dispose()-Issue" could be something like [ExcludeAutoExpose(nameof(Stream.Dispose()))]. This way an implementation could be done manually, taking into account all Traits that need disposing.

Yea, that's something that will be needed eventually. But it's going to require more brainpower than I have to get the API right.

Can confirm that MemoryStream works now. This is a great new feature.