Now in #SwiftLang review: The `@export` attribute, proposed by @dgregor79, is an expert library author’s utility knife. It does everything from replacing `@_alwaysEmitIntoClient` to helping Embedded Swift code encapsulate internal imports. Let us know what you think about it on the Swift Forums: https://forums.swift.org/t/se-0497-controlling-function-definition-visibility-in-clients/82666/1
Discussion
Loading...
Post
@beccadax @dgregor79 just so happened to find this very interesting discussion of using the build system to achieve some of the goals described for swift, but for c/++ systems https://www.gnu.org/software/gnulib/manual/html_node/Exported-Symbols-of-Shared-Libraries.html
@beccadax @dgregor79 having this in the compiler rather than the linker is clearly the better way to go but i'm impressed that this sort of discussion about fine-grained visibility is still occurring in the land of C
@beccadax And if you read my intro are are like, “What, I don’t need that!?”, it’s okay. We need expert tools, but nobody should feel like they have to stay on top of everything. When/if you need it, it’ll be there.
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled