# Missed optimization opportunity?

**URL:** <https://forums.swift.org/t/missed-optimization-opportunity/10381>\
**Category:** Standard Library\
**Tags:** performance\
**Created:** [February 27, 2018, 12:56pm UTC](https://forums.swift.org/t/missed-optimization-opportunity/10381 "2018-02-27T12:56:54Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Jens](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/jens/32/12903_2.png) [@Jens](https://forums.swift.org/u/Jens)\
**Post date:** [February 27, 2018, 9:32pm UTC](https://forums.swift.org/t/missed-optimization-opportunity/10381/6 "2018-02-27T21:32:36Z")

</div>

Many of the non-optimized ones (eg `.nextUp`, `.binade`, `.ulp`) seem to already be marked with:

```
@_inlineable // FIXME(sil-serialize-all)

```

While the optimized examples (eg `.magnitude`, `.squareRoot()`) seem to be marked also with `@_transparent`:

```
@_inlineable // FIXME(sil-serialize-all)
@_transparent

```

(I'm just looking [here](https://github.com/apple/swift/blob/master/stdlib/public/core/FloatingPointTypes.swift.gyb) and [here](https://github.com/apple/swift/blob/master/stdlib/public/core/FloatingPoint.swift.gyb) and am not particularly sure how to interpret things.)

---

_[View the full topic](https://forums.swift.org/t/missed-optimization-opportunity/10381)._