From b8f1491f6e9bfb509d66e646e3ba8efb64394e5d Mon Sep 17 00:00:00 2001 From: Yuki Okushi Date: Thu, 13 Jun 2019 00:37:30 +0900 Subject: [PATCH] Fix typos --- src/librustc/error_codes.rs | 2 +- src/test/ui/explain.stdout | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/librustc/error_codes.rs b/src/librustc/error_codes.rs index 6243e911bd5..65821d8dd83 100644 --- a/src/librustc/error_codes.rs +++ b/src/librustc/error_codes.rs @@ -1883,7 +1883,7 @@ extern "C" fn foo(userdata: Box) { # } ``` -The same applies to transmutes to `*mut fn()`, which were observedin practice. +The same applies to transmutes to `*mut fn()`, which were observed in practice. Note though that use of this type is generally incorrect. The intention is typically to describe a function pointer, but just `fn()` alone suffices for that. `*mut fn()` is a pointer to a fn pointer. diff --git a/src/test/ui/explain.stdout b/src/test/ui/explain.stdout index 411cdfb335b..9ea56271f59 100644 --- a/src/test/ui/explain.stdout +++ b/src/test/ui/explain.stdout @@ -53,7 +53,7 @@ This pattern should be rewritten. There are a few possible ways to do this: let f: extern "C" fn(*mut i32) = transmute(foo as usize); // works too ``` -The same applies to transmutes to `*mut fn()`, which were observedin practice. +The same applies to transmutes to `*mut fn()`, which were observed in practice. Note though that use of this type is generally incorrect. The intention is typically to describe a function pointer, but just `fn()` alone suffices for that. `*mut fn()` is a pointer to a fn pointer.