Google Git
Sign in
fuchsia/third_party/github.com/rust-lang/rust-analyzer/daaaff4492b7c0085a41e817bc6718a9c1ce5efc
commit
daaaff4492b7c0085a41e817bc6718a9c1ce5efc
[log]
author
Jacob Pratt <jacob@jhpratt.dev>
Wed Jun 24 00:40:22 2026 -0400
committer
GitHub <noreply@github.com>
Wed Jun 24 00:40:22 2026 -0400
tree
f97c0e0a768daf099f6f5faf32dd9283d260a694
parent
24ece7ba29cee2e1634d93b14ee19b27e6c3b190 [diff]
parent
8e61983aae46758352fe70e3b5cdb21d753c2320 [diff]
Rollup merge of #157946 - Jules-Bertholet:char-unassigned-private-use, r=Mark-Simulacrum

Make `char::is_private_use` and `char::is_assigned` unstably public

See also https://github.com/rust-lang/rust/pull/157944, https://github.com/rust-lang/rust/pull/154849. These functions are used in the implementation of `char::escape_debug()`, and there's no reason to force crates to duplicate data tables that std has to ship anyway. `is_assigned` is especially useful because crates relying on the stability guarantees of the other Unicode methods in `char` may wish to reject unassigned characters where those guarantees do not hold.

I'll add a tracking issue if this is approved.

The `is_assigned` vs `is_unassigned` bikeshed probably needs libs-API review before merging?

@rustbot label A-Unicode T-libs-api

r? @Mark-Simulacrum
tree: f97c0e0a768daf099f6f5faf32dd9283d260a694
  1. .cargo/
  2. .config/
  3. .github/
  4. .vscode/
  5. assets/
  6. bench_data/
  7. crates/
  8. docs/
  9. editors/
  10. lib/
  11. xtask/
  12. AGENTS.md ⇨ CLAUDE.md
  13. .codecov.yml
  14. .editorconfig
  15. .git-blame-ignore-revs
  16. .gitattributes
  17. .gitignore
  18. .typos.toml
  19. AI_POLICY.md
  20. Cargo.lock
  21. Cargo.toml
  22. CLAUDE.md
  23. clippy.toml
  24. CONTRIBUTING.md
  25. josh-sync.toml
  26. LICENSE-APACHE
  27. LICENSE-MIT
  28. PRIVACY.md
  29. README.md
  30. rust-version
  31. rustfmt.toml
  32. triagebot.toml
README.md

rust-analyzer is a language server that provides IDE functionality for writing Rust programs. You can use it with any editor that supports the Language Server Protocol (VS Code, Vim, Emacs, Zed, etc).

rust-analyzer features include go-to-definition, find-all-references, refactorings and code completion. rust-analyzer also supports integrated formatting (with rustfmt) and integrated diagnostics (with rustc and clippy).

Internally, rust-analyzer is structured as a set of libraries for analyzing Rust code. See Architecture in the manual.

codecov

Quick Start

https://rust-analyzer.github.io/book/installation.html

Documentation

If you want to contribute to rust-analyzer check out the CONTRIBUTING.md or if you are just curious about how things work under the hood, see the Contributing section of the manual.

If you want to use rust-analyzer's language server with your editor of choice, check the manual. It also contains some tips & tricks to help you be more productive when using rust-analyzer.

Security and Privacy

See the security and privacy sections of the manual.

Communication

For usage and troubleshooting requests, please use “IDEs and Editors” category of the Rust forum:

https://users.rust-lang.org/c/ide/14

For questions about development and implementation, join rust-analyzer working group on Zulip:

https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer

Quick Links

License

rust-analyzer is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0).

See LICENSE-APACHE and LICENSE-MIT for details.