From c640e550d8cd2e28ab500364d1d82a647cef1545 Mon Sep 17 00:00:00 2001 From: Oleg Zenzin Date: Thu, 19 Dec 2024 10:48:40 -0800 Subject: [PATCH] Fixing staging.md Example linked to obsolete macros-spec.md content Missed a wording still referencing obsolete content (thanks code reviewers for pointing it out) --- docs/_docs/reference/metaprogramming/staging.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/_docs/reference/metaprogramming/staging.md b/docs/_docs/reference/metaprogramming/staging.md index 3c5ea4515855..001ae622eabc 100644 --- a/docs/_docs/reference/metaprogramming/staging.md +++ b/docs/_docs/reference/metaprogramming/staging.md @@ -98,9 +98,9 @@ scala -with-compiler -classpath out Test ## Example Now take exactly the same example as in [Macros](./macros.md). Assume that we -do not want to pass an array statically but generate code at run-time and pass +do not want to pass a base double value statically but generate code at run-time and pass the value, also at run-time. Note, how we make a future-stage function of type -`Expr[Array[Int] => Int]` in line 6 below. Using `staging.run { ... }` we can evaluate an +`Expr[Double => Double]` in line 6 below. Using `staging.run { ... }` we can evaluate an expression at runtime. Within the scope of `staging.run` we can also invoke `show` on an expression to get a source-like representation of the expression.