From a47a00b5989cec33e6e3cf49d4b1d56b834c5683 Mon Sep 17 00:00:00 2001 From: Brian Staber Date: Wed, 3 Sep 2025 09:47:30 +0200 Subject: [PATCH] :recycle: [AR] Update book chapter --- book/src/ar_models.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/src/ar_models.md b/book/src/ar_models.md index 12df771..abd6905 100644 --- a/book/src/ar_models.md +++ b/book/src/ar_models.md @@ -273,7 +273,7 @@ ARModel fit_ar_yule_walkter(const std::vector &x) { - The class holds parameters + forecasting but the algorithms live outside. This way, I can add/replace estimators without modifying the class. -- `typename ARModel::Vector` — why the `typename`? Inside templates, dependent names might be types or values. `typename` tells the compiler it’s a type. +- `typename ARModel::Vector`: why the `typename`? Inside templates, dependent names might be types or values. `typename` tells the compiler it’s a type. - `std::array` vs `std::vector`? `std::array` is fixed-size (size known at compile time) and stack-allocated while `std::vector` is dynamic-size (runtime) and heap-allocated.