Looks good. Two questions:
-
I cannot find mention of whether or not the compiler has a right to optimize resources away. @Aciid said it made sense to him in the draft thread, but that he wanted to ask others’ thoughts first. Was it ever decided?
-
Is it possible to include a
.swift
or.c
file as a resource? One use case would be template files, like the ones SwiftPM produces for you withswift package init
. Should it be possible to register a path ending in.swift
withcopy(_:)
such that it would then be both included as a resource and prevented from being compiled into the target binary? (Or is there such thing as a use case for being both a resource and a compiled source at the same time?)