Rollup of 6 pull requests

[matthiaskrgr]

Successful merges:

• fix checking git submodules during a commit hook #126255 (fix checking git submodules during a commit hook)
• Pass target to some run-make tests #126355 (Pass target to some run-make tests)
• Rename InstanceDef -> InstanceKind #126567 (Rename InstanceDef -> InstanceKind)
• Fix broken documentation link #126579 (Fix broken documentation link)
• Add tracking issue number to async_drop APIs #126596 (Add tracking issue number to async_drop APIs)
• Update books #126603 (Update books)

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

[matthiaskrgr]

@bors r+ rollup=never p=6

[bors]

📌 Commit d5f9117 has been approved by matthiaskrgr

It is now in the queue for this repository.

[bors]

⌛ Testing commit d5f9117 with merge 04ab7b2...

[bors]

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing 04ab7b2 to master...

[rust-timer]

📌 Perf builds for each rolled up PR:

PR#	Message	Perf Build Sha
#126255	fix checking git submodules during a commit hook	abd043fa4126e470b249ac08cbd324c6891b7246 (link)
#126355	Pass target to some run-make tests	c97447a08249273df7df37cf42cb48f4d0c85d52 (link)
#126567	Rename InstanceDef -> InstanceKind	2724d3a8e4c7d020785cdad1380b8fcf8c949f36 (link)
#126579	Fix broken documentation link	9f35bfa7ce8f227299a39e88a37924b962f8bfb5 (link)
#126596	Add tracking issue number to async_drop APIs	09136d8d58bd34a418e53717268d5125531aab7f (link)
#126603	Update books	9929de3ec72cf3615aa8821832de6ca57a432ff8 (link)

previous master: 11380368dc

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

[rust-timer]

Finished benchmarking commit (04ab7b2): comparison URL.

Overall result: ❌ regressions - ACTION NEEDED

Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please open an issue or create a new PR that fixes the regressions, add a comment linking to the newly created issue or PR, and then add the perf-regression-triaged label to this PR.

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

Instruction count

This is a highly reliable metric that was used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	0.3%	[0.3%, 0.4%]	6
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	0.3%	[0.3%, 0.4%]	6

Max RSS (memory usage)

This benchmark run did not return any relevant results for this metric.

Cycles

Results (secondary 0.6%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	2.6%	[2.3%, 2.8%]	3
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-2.3%	[-2.5%, -2.2%]	2
All ❌✅ (primary)	-	-	0

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 670.379s -> 669.558s (-0.12%)
Artifact size: 320.52 MiB -> 320.53 MiB (0.00%)

[rylev]

The benchmarks impacted seem to now swing wildly back and forth with every run so this isn't a perf regression per say.

@rustbot label: +perf-regression-triaged