[swift-dev] Why are we re-linking?

[Dave Abrahams]

Can anyone explain why we're re-linking all these C++ executables when I
make changes only to the standard library?

[5/130] Linking CXX static library lib/libswiftBasic.a
[6/130] Linking CXX shared library lib/libswiftDemangle.dylib
[7/130] Linking CXX executable bin/swift
[8/130] Linking CXX executable bin/swift-demangle
[9/130] Linking CXX executable bin/sil-opt
[10/130] Linking CXX executable bin/swift-ide-test
[11/130] Linking CXX executable bin/lldb-moduleimport-test
[12/130] Linking CXX executable bin/sil-extract
[13/130] Linking CXX executable bin/swift-llvm-opt
[14/130] Linking CXX shared library lib/libsourcekitdInProc.dylib
[15/130] Linking CXX executable lib/sourcekitd.framework/Versions/A/XPCServices/SourceKitService.xpc/Contents/MacOS/SourceKitService
[16/130] Compiling /Users/dave/src/s/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/stdlib/public/core/macosx/x86_64/Swift.o
[17/130] Linking CXX shared library lib/sourcekitd.framework/Versions/A/sourcekitd
[18/130] Linking CXX executable bin/sourcekitd-test
[19/130] Linking CXX executable bin/sourcekitd-repl
[20/130] Linking CXX executable bin/complete-test

I imagine we might speed up stdlib development cycles a bit if we could
avoid that work.

Thanks,

-- 
Dave