fix: predict for TemplateExpressions

[MilesCranmer]

No description provided.

[github-actions]

Benchmark Results

	master	808bd10...	master/808bd10111a123...
search/multithreading	21 ± 1.8 s	22.2 ± 2.6 s	0.947
search/serial	35 ± 0.17 s	31.6 ± 0.24 s	1.11
utils/best_of_sample	2.05 ± 1.6 μs	2.26 ± 1.6 μs	0.907
utils/check_constraints_x10	12 ± 3.2 μs	12.1 ± 3.2 μs	0.992
utils/compute_complexity_x10/Float64	2.08 ± 0.11 μs	2.09 ± 0.11 μs	0.995
utils/compute_complexity_x10/Int64	2.01 ± 0.11 μs	2.09 ± 0.12 μs	0.961
utils/compute_complexity_x10/nothing	1.45 ± 0.13 μs	1.4 ± 0.1 μs	1.04
utils/insert_random_op_x10	6 ± 1.8 μs	5.84 ± 1.8 μs	1.03
utils/next_generation_x100	0.444 ± 0.1 ms	0.445 ± 0.12 ms	0.996
utils/optimize_constants_x10	0.0384 ± 0.0084 s	0.0369 ± 0.0088 s	1.04
utils/randomly_rotate_tree_x10	5.35 ± 0.62 μs	5.28 ± 0.59 μs	1.01
time_to_load	1.84 ± 0.056 s	1.84 ± 0.032 s	0.999

Benchmark Plots

A plot of the benchmark results have been uploaded as an artifact to the workflow run for this PR.
Go to "Actions"->"Benchmark a pull request"->[the most recent run]->"Artifacts" (at the bottom).

[coveralls]

Pull Request Test Coverage Report for Build 12060421186

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.003%) to 95.47%

---

Totals
Change from base Build 12060410166:	0.003%
Covered Lines:	3119
Relevant Lines:	3267

---

💛 - Coveralls