Doug Gregor 8713c13bef Centralize computation of the "code generation model" for object code & SIL ...

For a given function, we might end up emitting it's definition as
object code, serialized SIL, or both. The @export, @inlinable, and
@inline(always) attributes provide control of this behavior at the
declaration level.

Centralize the query function that will look for each of these
attributes and map down to a specific "code generation model", whose 3
options follow the naming from SE-0497: interface, inlinable, and
implementation. Use this one computation to back the queries for
"always emit into client", "never emit into client", and "inlinable"
so we can't get inconsistent results from places that are doing
one-off checks for these attributes.

2026-04-15 13:03:55 -07:00

..

ScanningLoaders.h

[Dependency Scanning] Warn, instead of fail, when a Swift dependency query only finds modules built for incompatible target

2025-10-15 16:58:50 -07:00

Serialization.h

Serialization: Break the cycle between Serialization and SymbolGraphGen.

2022-10-29 21:37:09 -07:00

SerializationOptions.h

Serialization: Option to skip writing decls marked @_implementationOnly

2025-11-11 13:03:15 -08:00

SerializedModuleLoader.h

Teach canImport to reject modules that mismatch on Embedded vs. normal Swift

2026-04-02 18:31:32 -07:00

SerializedSILLoader.h

[SILGen] Consistently use SIL asmname for foreign function/variable references

2025-10-29 19:35:55 -07:00

Validation.h

Centralize computation of the "code generation model" for object code & SIL

2026-04-15 13:03:55 -07:00