# SE-0394: Package Manager Support for Custom Macros

**URL:** <https://forums.swift.org/t/se-0394-package-manager-support-for-custom-macros/64170>\
**Category:** Proposal Reviews\
**Tags:** packagemanager, macros\
**Created:** [April 3, 2023, 10:40pm UTC](https://forums.swift.org/t/se-0394-package-manager-support-for-custom-macros/64170 "2023-04-03T22:40:39Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![NeoNacho](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/neonacho/32/1368_2.png) [@NeoNacho](https://forums.swift.org/u/NeoNacho)\
**Post date:** [April 5, 2023, 1:18am UTC](https://forums.swift.org/t/se-0394-package-manager-support-for-custom-macros/64170/4 "2023-04-05T01:18:44Z")

</div>

> [@grynspan](#):
>
> The name `.macro()` seems a bit off, because it's used to define a macro _target_, not an individual macro. I'd suggest `.macroTarget()` for consistency with e.g. `.testTarget()`.

This is intentional, we're (slowly) trying to move away from having the target suffix since it is implied by the context. We did the same thing for plugins and eventually we'd like to have e.g. `.test()` as well.

> [@grynspan](#):
>
> One thing the proposed interface is missing is support for language settings (e.g. `.define()`) as is available for other target types.

This is a good point, it came up during the initial pitch and I neglected to add this.

---

_[View the full topic](https://forums.swift.org/t/se-0394-package-manager-support-for-custom-macros/64170)._