I wonder if we really are no longer depending on the full Foundation, considering we don't have these flags enabled to make sure we don't have any "implicit" unintended imports:

        .enableUpcomingFeature("MemberImportVisibility"),
        .enableUpcomingFeature("InternalImportsByDefault"),

perhaps this should be for another PR? The flags might require a decent amount of explicit imports to be added.

I wonder if we really are no longer depending on the full Foundation, considering we don't have these flags enabled to make sure we don't have any "implicit" unintended imports:

        .enableUpcomingFeature("MemberImportVisibility"),
        .enableUpcomingFeature("InternalImportsByDefault"),

perhaps this should be for another PR? The flags might require a decent amount of explicit imports to be added.

I added the flags, the only change needed was to make the import of Logging (which itself does not use Foundation) and the C libraries public. The C struct tm is used in one of our public structs. Here is the commit

I'd wait for Tim/Gwynne review as well.

I'd wait for Tim/Gwynne review as well.

Whoops. 😅

Ah 😅 should be fine