# SE-0496: \`@inline(always)\` Attribute

**URL:** <https://forums.swift.org/t/se-0496-inline-always-attribute/82480>\
**Category:** Proposal Reviews\
**Tags:** performance, optimizations\
**Created:** [October 2, 2025, 1:26pm UTC](https://forums.swift.org/t/se-0496-inline-always-attribute/82480 "2025-10-02T13:26:53Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Douglas\_Gregor](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/douglas_gregor/32/1362_2.png) [@Douglas\_Gregor](https://forums.swift.org/u/Douglas_Gregor)\
**Post date:** [October 2, 2025, 3:36pm UTC](https://forums.swift.org/t/se-0496-inline-always-attribute/82480/4 "2025-10-02T15:36:31Z")

</div>

> [@ricketson](#):
>
> The proposal mentions `@_alwaysEmitIntoClient`, but only in passing in one of the code examples when discussing interactions with `@inlinable`. Even though `@_alwaysEmitIntoClient` is an underscore’d attribute, can the proposal add more clarity about how we should expect this new attribute to interact with it?

There is a separate [pitch thread](https://forums.swift.org/t/pitch-controlling-function-definition-visibility-in-clients/82372) about formalizing `@_alwaysEmitIntoClient`, which goes into depth on the relationship.

Doug

---

_[View the full topic](https://forums.swift.org/t/se-0496-inline-always-attribute/82480)._