[swift-dev] sharing tips and tricks and scripts
clattner at nondot.org
Sat Oct 21 11:10:43 CDT 2017
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.
> On Oct 17, 2017, at 6:05 PM, Jordan Rose via swift-dev <swift-dev at swift.org> wrote:
> 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.)
>> On Oct 17, 2017, at 17:25, Erik Eckstein via swift-dev <swift-dev at swift.org> wrote:
>> 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 document contains many useful little things which might help debugging the compiler.
>> So with this email I want to “announce” this, because I found that many people didn’t know that.
>> And also I’d like to encourage everyone to contribute to DebuggingTheCompiler.rst and other documents.
>> Another thing is that many people have implemented their own little helper scripts for various purposes, which they share by email with others and those emails get lost, and nobody knows what’s the latest version of a script, etc.
>> We have many of such scripts already in utils. But utils got already very convoluted. So I propose to create a sub-folder, e.g. ‘dev-scripts’ to place such scripts (just for new scripts, I’m not proposing moving existing scripts). The intention is to keep the bar low to contribute to dev-scripts. So scripts may be not super-polished and it’s also ok to have multiple scripts which do similar things.
>> Some scripts might get attention and turn out to be useful for many people and thus get improved over time. We can eventually move such scripts out of dev-scripts into the “production” folder utils.
>> Please let me know if you have any comments.
>> swift-dev mailing list
>> swift-dev at swift.org
> swift-dev mailing list
> swift-dev at swift.org
More information about the swift-dev