]> git.lizzy.rs Git - rust.git/commit - src/tools/rust-analyzer
projects / rust.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(merge: 871cf2b 49aa5ba)
Rollup merge of #91467 - ChrisDenton:confusing-os-string, r=Mark-Simulacrum
authorMatthias Krüger <matthias.krueger@famsik.de>
Wed, 8 Dec 2021 10:08:58 +0000 (11:08 +0100)
committerGitHub <noreply@github.com>
Wed, 8 Dec 2021 10:08:58 +0000 (11:08 +0100)
commitbb8a4ab6aed4b96fe2338b0f59f67d4560d4ba11
tree3b62ac89dc360aa2bd69b10c79f71494cf46cf29tree | snapshot
parent871cf2bc9e4221ec1dfdcfdb3f8d66ab42d6201bcommit | diff
parent49aa5baf36feb22818d8614b43f24f73e530d884commit | diff
Rollup merge of #91467 - ChrisDenton:confusing-os-string, r=Mark-Simulacrum

Emphasise that an OsStr[ing] is not necessarily a platform string

Fixes #53261

Since that issue was filed, #56141 added a further clarification to the `OsString` docs. However the ffi docs may still leave the impression that an `OsStr` is in the platform native form. This PR aims to further emphasise that an `OsStr` is not necessarily a platform string.
Empowering everyone to build reliable and efficient software.