From 02d0b5d01a0f9c305268578666a355d8e1f77e32 Mon Sep 17 00:00:00 2001 From: Lukasz Anforowicz Date: Fri, 1 Dec 2023 08:21:20 +0000 Subject: [PATCH] Chromium: fix path of `String::from_utf16` (#1541) --- src/exercises/chromium/bringing-it-together.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/exercises/chromium/bringing-it-together.md b/src/exercises/chromium/bringing-it-together.md index 052c8f36..ab97a8ad 100644 --- a/src/exercises/chromium/bringing-it-together.md +++ b/src/exercises/chromium/bringing-it-together.md @@ -38,7 +38,7 @@ Students will likely need some hints here. Hints include: UTF8, and will probably decide that it's better to do the conversion on the C++ side using `base::UTF16ToUTF8` and back again. * If students decide to do the conversion on the Rust side, they'll need to - consider [`std::string::from_utf16`][1], consider error handling, and + consider [`String::from_utf16`][1], consider error handling, and consider which [cxx supported types can transfer a lot of u16s][2]. * Students may design the C++/Rust boundary in several different ways, e.g. taking and returning strings by value, or taking a mutable reference