Using Sketch Symbols as a Trust Boundary in a Design System
Learn how Sketch Symbols form a reusable UI component layer, where the master Symbol acts as a trust boundary, instances can be safely overridden, and library updates propagate predictably.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how Sketch Symbols form a reusable UI component layer, where the master Symbol acts as a trust boundary, instances can be safely overridden, and library updates propagate predictably.
Problem When building a shared library, global symbols that are not intended for external use can be inadvertently exported, leading to namespace pollution or security concerns. The C language provides the static keyword for internal linkage, but the default visibility rules differ across compilers and platforms. Additionally, visibility attributes and linke
When building a shared library with -fvisibility=hidden , the goal is to keep all non‑static symbols hidden unless explicitly marked default. However, the treatment of inline functions defined in header files is not settled across GCC releases; some versions emit such functions with default visibility when they are not eliminated, while others respect the hi
Goal: Assess whether GCC 12 could enable link‑time optimization by default for static libraries when the -fuse-linker-plugin flag is present, similar to the behavior already applied to shared libraries. Constraints: The documentation explicitly states that static libraries still require -flto to activate LTO, and the change to shared‑library defaults does no