From 28a9eed73ce336442d358cbe12c4f2c09835efb8 Mon Sep 17 00:00:00 2001 From: Jared Harp Date: Sun, 4 Dec 2022 20:57:02 -0500 Subject: [PATCH] Fix small inaccuracy in monomorph page --- src/doc/rustc-dev-guide/src/backend/monomorph.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/doc/rustc-dev-guide/src/backend/monomorph.md b/src/doc/rustc-dev-guide/src/backend/monomorph.md index 21a7882031b2..4a0b55f6249b 100644 --- a/src/doc/rustc-dev-guide/src/backend/monomorph.md +++ b/src/doc/rustc-dev-guide/src/backend/monomorph.md @@ -10,7 +10,7 @@ execute. Different languages handle this problem differently. For example, in some languages, such as Java, we may not know the most precise type of value until runtime. In the case of Java, this is ok because (almost) all variables are -reference values anyway (i.e. pointers to a stack allocated object). This +reference values anyway (i.e. pointers to a heap allocated object). This flexibility comes at the cost of performance, since all accesses to an object must dereference a pointer.