Monday, May 23, 2016

Welcome to the one hundred and twenty-fifth issue of LLVM Weekly, a weekly
newsletter (published every Monday) covering developments in LLVM, Clang, and
related projects. LLVM Weekly is brought to you by Alex
Bradbury. Subscribe to future issues at
http://llvmweekly.org and pass it on to anyone else you think may be
interested. Please send any tips or feedback to asb@asbradbury.org, or @llvmweekly or @asbradbury on Twitter.

This week I discovered the Swift Weekly Brief
newsletter. Its author, Jesse Squires does a
wonderful job of summarising mailing list traffic, recent commits, and
discussions on swift-evolution proposals. If you have an interest in Swift
development or language design in general I highly recommend it.

Are you interested in writing for the LLVM
blog? Or
volunteering to help recruit content authors? If so, get in touch with Tanya.

Quentin Colombet has summarised recent discussion on policies to help
release
management and
detailed the automatic hooks he hopes to explore next for updating bugs when
referenced in a commit message. The following discussion looked at how these
hooks may be implemented and what level of rigidity would be most beneficial
to the community.