Skip to content

Conversation

nnethercote
Copy link
Contributor

A bunch of minor things I found while looking over this code.

It's in the wrong place, and it's empty.

There is also `.github/ISSUE_TEMPLATE/bug_report.md`, which is in the
right place.
To clarify something I found hard to understand.
It mixes up `debug_printf!` and `debug_printfln!`.
@Firestar99
Copy link
Member

Can you manually squash this PR? To not pollute history too much

(You can't configure merge queue to squash on a per-PR basis, it only squashes all PRs or none... please github add that)

@nnethercote
Copy link
Contributor Author

I'd rather not squash the commits, because they are logically separate

I'm a strong believer in using separate commits for logically separate changes, and not squashing unrelated commits. I put effort into this because separate commits make reviewing easier, they make version control archaeology easier, and they make bisection easier if a bug is introduced. Separate commits don't pollute history; if anything, squashing unrelated changes into a single commit pollutes history.

(Of course, sometimes squashing is appropriate, e.g. when you have a messy commit series like "add feature" / "fix the test" / "run rustfmt" / "fix a typo in the test" where the commits aren't logically separate and merely reflect local version control history. This PR isn't one of those cases.)

@nazar-pc
Copy link
Contributor

(You can't configure merge queue to squash on a per-PR basis, it only squashes all PRs or none... please github add that)

Add vote to this one: https://github.com/orgs/community/discussions/68723

@Firestar99 Firestar99 added this pull request to the merge queue Sep 24, 2025
Merged via the queue into Rust-GPU:main with commit dfcff49 Sep 24, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants