I agree that fixing build-script is the better approach than to introduce
another wrapper around it.
But there are many other needs for scripts, for example the (already existing)
cmpcodesize script for comparing code size.
And I think it makes sense to create a new directory rather than puttin
I agree with Jordan (and Chris) on this. I think that we should try to
simplify the build process that we have rather than encouraging more build
script wrappers. The current build process is pretty cumbersome which is
why I think that many people have wrapper scripts. In fact, it seems that
it
Any scripts should be subject to the same code review and design policies as
the rest of the compiler. A bisection script or build-script seem fine, but a
four line script to automate something is probably not the right thing to
include.
-Chris
> On Oct 17, 2017, at 6:05 PM, Jordan Rose via s
I always dislike wrapper scripts because it means that people are working
around undesirable behavior in a tool rather than fixing it. But that doesn't
seem to be a practical answer, because people are already using wrapper
scripts. (I've lost this argument several times before.)
Jordan
> On
I recently had some discussions about how to share those little tips and tricks
which everyone has to make building, debugging, etc. the swift compiler easier.
And actually we already have a central place for this: it’s the docs folder in
the swift repo. Especially the DebuggingTheCompiler.rst d
