RepoJournal
Mobile platforms

Mobile platforms

Flutter, Swift, and Kotlin - the mobile platforms developers ship on

Keep up with Mobile platforms in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

One email a day. Unsubscribe in one click.

Pick a date

Topics: Mobile Full archive →

The Wire · Showcase

SWIFT COMPILER GETS NATIVE INSTRUCTION ORDERING, FLUTTER DOCS TARGETING CONTRIBUTOR PAIN

By RepoJournal · Filed · About Mobile platforms

Apple's Swift team shipped a foundational compiler optimization that replaces on-demand instruction indexing with persistent per-instruction ordering, cutting O(n) overhead from every pass that needs to compare instruction positions.

The Swift changes land across three related commits: native instruction ordering via persistent indices [1], a new LargeCustomBits structure to support larger instruction indices [3], and removal of the old InstructionIndices data structure [4]. This is the kind of underneath-the-hood work that doesn't ship features but makes the compiler faster and cleaner. LinearLifetimeChecker, SILVerifier, and BoundsCheckOpts all stopped maintaining their own copies and now use a single persistent ordering mechanism.

On the Flutter side, the packages team is tightening contributor onboarding by reworking the CHANGELOG documentation [2]. New contributors were misusing the NEXT section at alarming rates because the docs led with the uncommon case instead of the common one. The rework puts the standard version bump workflow first, edge cases second, which is how documentation should work for people learning the codebase.

Swift's embedded layer also got cleaner this cycle [5]. The allocation and free operations now take a flags parameter set that can extend in the future (currently just calloc-like memory clearing), and the naming shifted from _swift_aligned* to _swift_allocate and _swift_free with ptrdiff_t instead of int for better Swift type mapping.

On the Kotlin side, the JS backend is implementing supertype approximation in TypeScript export [6], and the compiler got better diagnostics for inapplicable fallbacks [7]. These are smaller wins but they're shipping across all three major mobile platform ecosystems.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] SIL: native instruction ordering via persistent instruction indices ↗ apple/swift
  2. [2] Rework docs for flutter/packages changelogs ↗ flutter/flutter
  3. [3] SIL: add LargeCustomBits in SILNode to support large instruction indices apple/swift
  4. [4] SIL: remove `InstructionIndices` and use `SILInstruction::isBeforeInBlock` instead apple/swift
  5. [5] [Embedded] Clean up the abstraction layer and add alloc/free flags ↗ apple/swift
  6. [6] [JS] Implement supertype approximation in Analysis API-based TypeScript export ↗ JetBrains/kotlin
  7. [7] KT-86482: separate diagnostic for inapplicable fallback ↗ JetBrains/kotlin

Quick answers

What shipped in Mobile platforms on June 15, 2026?
Apple's Swift team shipped a foundational compiler optimization that replaces on-demand instruction indexing with persistent per-instruction ordering, cutting O(n) overhead from every pass that needs to compare instruction positions. In total, 22 commits and 14 pull requests landed.
Who contributed to Mobile platforms on June 15, 2026?
5 developers shipped this update, including eeckstein, stuartmorgan-g, DougGregor, broadwaylamb, and GrigoriiSolnyshkin.
What were the notable Mobile platforms updates?
SIL: native instruction ordering via persistent instruction indices, Rework docs for flutter/packages changelogs, and SIL: add LargeCustomBits in SILNode to support large instruction indices.

More from Mobile platforms

Daily updates, in your inbox

Follow Mobile platforms

Keep up with Mobile platforms in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?

We use privacy-friendly analytics (Google Analytics, IP-anonymized) to see which pages help readers. No ads, and we never sell your data. See our Privacy Policy.