The release notes this week actually put in an SDK path here. Fortunately
it's the one that matches what plenty of people are using (10.9 public SDK
from an Xcode in Applications), but it's not the best thing to use.
Swift SVN r13488
The debug info caveat sounds worse than it is, since you already have to
recompile all the source files in a module when any of them change.
Swift SVN r13471
The LLDB project requires an LLVM project containing both clang and
swift, while buildbot-script builds swift outside the LLVM tree. The
obvious choice, if you don't want two copies of the source on your
system, is to symlink swift into llvm's tools directory. Yes, building
lldb will still build llvm and swift again, but that's a problem for
another day. To avoid building swift a /third/ time as part of swift's
LLVM build, we need to tell the buildbot-script to ignore that symlink
if it's there.
Swift SVN r13412
New files automatically get the LLVM header if you enable
auto-insert-mode. You can also generate one explicitly in any file
using `M-x llvm-header'. Along the way, factored settings specific to
the Swift project out of swift-mode.el and put them in
swift-project-settings.el
Swift SVN r13319
Also, don't allow file-relative imports (i.e. don't consider a /source file's/
location as an include path). Both of these should be requested by the user,
at least at this point.
Swift SVN r13249
Because this is useful in testing, I've left in a frontend option
-enable-source-import for both swift and swift-ide-test that sidesteps the
module restriction. Right now, though, this is the right thing to avoid
users running into strange issues when they import another file within
their module and Swift treats it as a separate module.
<rdar://problem/15937521>
Swift SVN r13248
You can still request sourcekit by passing -s on the command-line.
Along the way, buildbot-script.sh now tolerates missing SourceKit
sources if it is being asked to skip the SourceKit build.
Swift SVN r13170
This keeps us from having to deal with fat swiftmodules for now.
In the long run we're hoping to solve this problem with build configurations,
so that a single module file can support multiple architectures.
(See <rdar://problem/15056323>)
<rdar://problem/15204953>
Swift SVN r13135
This benchmark needs some love. Care needs to be taken to run it several
times and average the result, BUT not resort the sorted array.
Swift SVN r12865
One might wonder, why not just not use mach_absolute_time in the swift program
instead. The reason why is that using mach_absolute_time in this manner filters
out process startup noise as well as anything in the program we do not want to
time.
Swift SVN r12793
