Revision as of 03:46, 18 October 2021 edit Tcpp (talk \| contribs) 14 edits →Language extensions: snake_case is normative for attribute macro names Tag: Visual edit ← Previous edit		Revision as of 03:50, 18 October 2021 edit undo Tcpp (talk \| contribs) 14 edits →Language extensions: Procedural macros can be user-defined, too, so calling declarative macros user-defined is a false contrast Tag: Visual edit Next edit →
Line 163: It is possible to extend the Rust language using the procedural macro mechanism.<ref name="rust-procedural-macros">{{cite web \|url=https://doc.rust-lang.org/reference/procedural-macros.html \|title=Procedural Macros \|website=The Rust Programming Language Reference \|access-date=23 Mar 2021 \|archive-date=7 November 2020 \|archive-url=https://web.archive.org/web/20201107233444/https://doc.rust-lang.org/reference/procedural-macros.html \|url-status=live }}</ref> Procedural macros use Rust functions that run at compile time to modify the compiler's token stream. This complements the ~~user-defined~~declarative macro mechanism (also known as ''macros by example''), which uses pattern matching to achieve similar goals. Procedural macros come in three flavors:

Rust (programming language): Difference between revisions