The documented patterns for some compiler builtin macros are subtly incorrect #46242
Labels
A-docs
Area: Documentation for any part of the project, including the compiler, standard library, and tools
Example: The macro
env
is documented aswhen in reality, the following call is legal (playground):
I believe this is because the definition in std is just a fake stub.
concat!
andconcat_idents!
(edit: alsoformat_args!
) are in a similar boat (they also support trailing commas in places where the documented pattern suggests they would not).In all fairness this is not a big deal, and even has the conceivable benefit that the documentation is cleaner without such laser precision. I just thought it was worth making an issue for.
The text was updated successfully, but these errors were encountered: