stackotter

+1 to this! I've got a [fork](https://github.com/stackotter/Socket) which fixes this issue but it'd be good to be able to merge this in to the source repo so that development doesn't...

Ok, If I get the time I'll have a look into making some comparable benchmarks for Metal, swift-webgpu and Dawn. Are there any features in particular that you think would...

> [Pointfree's case paths](https://github.com/pointfreeco/swift-case-paths) macro essentially does this amongst other things 😉 Woah, thanks for bringing that to my attention! I hadn't checked out case paths since macros, didn't realise...

Yeah definitely 👍

Awesome! I reckon classRestriction should map to the nominal type `AnyObject` (iirc it’s equivalent to that but I may be mistaken), metatype should be mapped to the member type `X.Type`...

Hey Alessio, happy to review this PR but I've just been holding off cause it's still marked as a draft. Just letting you know in case that was an accident...

> As a source of truth for what the normalized version should be, I used, where possible, the result obtained by printing the type to the console, for example: >...

> Even considering that `Void` is generally preferable over `()` in Swift, we are here trying to normalize types to their most basic form, not trying to make them look...

So sorry, this completely slipped my mind! I just went back and found the responses to the question. I only got one response from a Swift programmer (who thought `Void`...

> * I would consider using [`swift-macro-testing`](https://github.com/pointfreeco/swift-macro-testing) for tests Woah that looks really clean, will definitely consider switching to that at some point! But yeah it should be a separate...