diff options
| author | bors <bors@rust-lang.org> | 2023-08-30 18:12:28 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-08-30 18:12:28 +0000 |
| commit | 321334429efd79e9db2b85e43c8f91eb2ce60f6c (patch) | |
| tree | c3e317dc9c11c8d84271eeb4471a14e280c4efcb | |
| parent | b06503b6ec98c9ed44698870cbf3302b8560b442 (diff) | |
| parent | ea74cc4b9a159087177506fecc1ce900468a0ef1 (diff) | |
| download | rust-321334429efd79e9db2b85e43c8f91eb2ce60f6c.tar.gz rust-321334429efd79e9db2b85e43c8f91eb2ce60f6c.zip | |
Auto merge of #15534 - rust-lang:Veykril-patch-1, r=Veykril
Update architecture.md
| -rw-r--r-- | docs/dev/architecture.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/dev/architecture.md b/docs/dev/architecture.md index 895de5798ac..b7d585cafb3 100644 --- a/docs/dev/architecture.md +++ b/docs/dev/architecture.md @@ -268,7 +268,7 @@ They are independent from the rest of the code. And it also handles the actual parsing and expansion of declarative macro (a-la "Macros By Example" or mbe). For proc macros, the client-server model are used. -We pass an argument `--proc-macro` to `rust-analyzer` binary to start a separate process (`proc_macro_srv`). +We start a separate process (`proc_macro_srv`) which loads and runs the proc-macros for us. And the client (`proc_macro_api`) provides an interface to talk to that server separately. And then token trees are passed from client, and the server will load the corresponding dynamic library (which built by `cargo`). |
