Dr. Mickey Lauer

Unfortunately not – at the time I was in a hurry and so I couldn't dive deep enough in to XMLCoder to make it happen. Thus, I resorted to a...

@MaxDesiatov Do you have any opinion on the `namespace` proposal?

@MaxDesiatov Please see the following (not working) demo which hopefully explains how I would imagine the look and feel at the call site: ```swift import XMLCoder /** Goal is to...

Well, in that case we could make it an (optional?) non-static property in the protocol and have it set as part of the element construction. The dictionary conveys more semantics,...

Let me add: Of course, I can implement all that on top of XMLCoder, it just feels more natural — to me at least — to have builtin support for...

> > Well, in that case we could make it an (optional?) non-static property in the protocol and have it set as part of the element construction. > > >...

Have you run it through instruments to find out any potential hotspots?

Perhaps https://github.com/Cornucopia-Swift/CornucopiaUDS might be helpful.

Could you create a pull request, please?

In my local copy I'm using the following patch: ```swift diff --git a/Sources/SlideOverCard/SlideOverCard.swift b/Sources/SlideOverCard/SlideOverCard.swift index 772e279..8c597ee 100644 --- a/Sources/SlideOverCard/SlideOverCard.swift +++ b/Sources/SlideOverCard/SlideOverCard.swift @@ -54,6 +54,7 @@ public struct SlideOverCard: View {...