diff options
| author | Jacob Pratt <jacob@jhpratt.dev> | 2024-12-17 05:37:00 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-12-17 05:37:00 -0500 |
| commit | 7e72c3e82f0fa44b7f1ff9d29994e7369d800c98 (patch) | |
| tree | a082a3e720d501c34e878b9e2e9c0c157cf4e56b /tests/rustdoc-js-std/parser-slice-array.js | |
| parent | e7407b3029e629c83729c6cc5a1051b0ed62cb62 (diff) | |
| parent | c58219b7865f0db81866b3000be585780f5c0758 (diff) | |
| download | rust-7e72c3e82f0fa44b7f1ff9d29994e7369d800c98.tar.gz rust-7e72c3e82f0fa44b7f1ff9d29994e7369d800c98.zip | |
Rollup merge of #134365 - Zalathar:builder, r=nnethercote
Rename `rustc_mir_build::build` to `builder` GitHub's “Go to file” feature silently ignores all files in this module, presumably because they are in a directory named `build`, which is mistaken for a build-output directory. That makes it meaningfully harder to view those files and their history via GitHub. This PR sidesteps that issue by renaming `build` to `builder`, which in context has basically the same meaning, but can't be mistaken for a build-output directory. --- Extracted from #133404, after #133592 changed the .gitignore rule from `build/` to `/build`. The problem of GitHub ignoring these files still exists even after that change, which suggests that GitHub's behaviour is a hard-coded heuristic that isn't influenced by the repository's git settings. Currently this PR doesn't include the tidy rule forbidding `build` as a module name, but that could be added if people think it's a good idea.
Diffstat (limited to 'tests/rustdoc-js-std/parser-slice-array.js')
0 files changed, 0 insertions, 0 deletions