Why the compiler doesn't just assume @inliable by default for all symbols in non-resilient modules/builds?

Lots of Swift codes use @inlinable nowadays, a simple search in apple / swiftlang org shows a lot of its occurrences: Code search results · GitHub Are there any downsides to have @inlinable/@useableFromInline by default enabled on all symbols, for non-resilient modules / builds? Can the compiler possibly implement that? Would help a lot in not having to litter our code with those attributes. A quick search in swift-nio shows 1300+ @inlinable in Sources/**/*.swift and 500+ @usableFromInline. T...