jextract: Evaluate `IfConfigDecl` for simple patterns

[sidepelican]

When generating .swiftinterface files using the -emit-module-interface flag, unexpected #if blocks are often generated. For example:

• Original .swift

public struct AppStore: Sendable, Codable {
  public var storeURL: URL?
  public init(storeURL: URL?) {
    self.storeURL = storeURL
  }
}

• Generated .swiftinterface

public struct AppStore : Swift.Sendable, Swift.Codable {
  public var storeURL: Foundation.URL?
  #if compiler(>=5.3) && $NonescapableTypes
  public init(storeURL: Foundation.URL?)
  #endif
  public func encode(to encoder: any Swift.Encoder) throws
  public init(from decoder: any Swift.Decoder) throws
}

The Problem

The exact reason for this behavior is unclear, but expressions like #if compiler(>=5.3) && $NonescapableTypes appear in various places within generated interfaces.

Currently, Swift2JavaVisitor ignores IfConfigDecl entirely.
As a result, any method or property signatures wrapped in these #if blocks are lost.

Proposed Solution

We could potentially use SwiftIfConfig to evaluate these blocks.

Although providing a full BuildConfiguration might be complex, it would be highly beneficial to at least support simple, common patterns.

[ktoso]

IfConfig is probably the way, wdyt @DougGregor since you worked on that could you chime in if it's appropriate to extend parsing here to handle code in those blocks?

[DougGregor]

SwiftIfConfig is good for handling #ifs, but it's not easy to know what build configuration to use with it. Recent compilers (Swift 6.3+) have an option to spit out a static build configuration for a particular target triple, but I don't think jextract really knows the target triple. I suppose you could bake a stripped-down version of the static build configuration into jextract and use that consistently. #if os(...) wouldn't be evaluated, but hasFeature could work with a fixed set of features.

[ktoso]

Worst case maybe we'd have to pass in either enabled features or os-es explicitly to jextract via config or env and it'd pass it along to ifconfig 🤔

swift-frontend -print-static-build-config is helpful but not quite enough AFAICS, and we wouldn't have a good way to call that probably anyway?

Would you want to look into that @sidepelican ?

[ktoso]

I merged this too eargerly; it had some issues #676

[sidepelican]

Resolved again in #678