feat: introduce WireMacros - no ticket #1694
Conversation
| let uuid = #UUID("7411ca17-ba08-4905-92d2-0617a8c810ca") | ||
| print(uuid) |
There was a problem hiding this comment.
Should these lines here?
There was a problem hiding this comment.
This main file is kind of a playground to develop the macros.... maybe it's not needed since we can do that in tests and/or in our other modules.
|
added an example how to use it in |
| // Targets are the basic building blocks of a package, defining a module or a test suite. | ||
| // Targets can depend on other targets in this package and products from dependencies. |
There was a problem hiding this comment.
I'd probably remove these two lines of comments
There was a problem hiding this comment.
Nice! I'm super in favor of adding macros if we can keep the compile performance costs are not prohibitive - especially those which can get rid of unnecessary optional values as these tend explode.
I would also consider adding something like #URL("http://example.com")
| import Foundation | ||
|
|
||
| /// A macro that, when attached to a protocol declaration, produces a | ||
| /// companion "provider" protocol that can be used inject dependencies. |
There was a problem hiding this comment.
This is pretty interesting. I need to take a look to understand the provider pattern more
Issue
Create a
WireMacrospackage:@Providedgenerates a "provider" companion protocol for other protocols.#UUIDvalidates uuid strings at compile time.Open question: is the potential overhead of using macros a concern?
Checklist
[WPB-XXX].