Extracting experimental feature flags into a separate file so that we
can add Allan as a code owner of just that file. He has to deal with
breakage when folks remove these flags improperly.
The declarations for the well-known function entries for the Swift
runtime have direct impact on the Swift runtime implementation for
Windows. Add myself as a CODEOWNER to provide notifications of any
changes that may impact platform support.
This is a tool specifically designed to generate
Xcode projects for the Swift repo (as well as a
couple of adjacent repos such as LLVM and Clang).
It aims to provide a much more user-friendly experience
than the CMake Xcode generation (`build-script --xcode`).
The primary change here is to add @hamishknight to directories he was missing, but while here:
- Use alphabetical order for changed files/directories
- Add all @ahoppen / @bnbarham / @hamishknight / @rintaro for any area
that one of us is an owner of and remove @zoecarver
- Add @ahoppen / @bnbarham / @hamishknight / @rintaro to ASTGen
The top-level stdlib directory has been claimed by the stdlib team,
so we should probably grab public/runtime and public/Threading to
make sure that we get pinged about changes to those.
Mark myself as an owner for the vim support files. This should help auto-add review requests to help ensure that these changes can get merged rather than languishing.
swift-evolve hasn’t been used in the recent past. @beccadax and I agreed that it doesn’t provide any value anymore to keep swift-evolve around. In Becca’s words:
> The resilience implementation is pretty stable at this point, and it never seems to have had many of the bugs that swift-evolve would have been able to shake out.
This makes sure that folks who use clang-tidy see consistent code analysis reports. This is especially helpful for those using IDEs with clang-tidy integration.
The config file is based on the LLVM `.clang-tidy` file: https://github.com/llvm/llvm-project/blob/main/.clang-tidy
Add some implicit reviewers for `swift-inspect`. @mikeash and @al45tair
are obvious candidates, and I've done a small amount of contribution to
the tool as well.
I'd love to be notified for PRs in those without grepping PR titles so proposing to add myself here.
More than happy to include more folks? Would it make sense to include e.g. @hborla @DougGregor ?
