Skip to content

Commit

Permalink
[Documentation: Macros] Use some more SSL
Browse files Browse the repository at this point in the history
  • Loading branch information
genodeftest committed Jun 4, 2015
1 parent 3c0165d commit 2abffd5
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions src/doc/trpl/macros.md
Expand Up @@ -224,7 +224,7 @@ more" match. Both forms optionally include a separator, which can be any token
except `+` or `*`.

This system is based on
"[Macro-by-Example](http://www.cs.indiana.edu/ftp/techreports/TR206.pdf)"
"[Macro-by-Example](https://www.cs.indiana.edu/ftp/techreports/TR206.pdf)"
(PDF link).

# Hygiene
Expand Down Expand Up @@ -319,7 +319,7 @@ syntax context where it was introduced. It’s as though the variable `state`
inside `main` is painted a different "color" from the variable `state` inside
the macro, and therefore they don’t conflict.

[hygienic macro system]: http://en.wikipedia.org/wiki/Hygienic_macro
[hygienic macro system]: https://en.wikipedia.org/wiki/Hygienic_macro

This also restricts the ability of macros to introduce new bindings at the
invocation site. Code such as the following will not work:
Expand Down Expand Up @@ -622,7 +622,7 @@ invocation gives you another opportunity to pattern-match the macro’s
arguments.

As an extreme example, it is possible, though hardly advisable, to implement
the [Bitwise Cyclic Tag](http://esolangs.org/wiki/Bitwise_Cyclic_Tag) automaton
the [Bitwise Cyclic Tag](https://esolangs.org/wiki/Bitwise_Cyclic_Tag) automaton
within Rust’s macro system.

```rust
Expand Down

0 comments on commit 2abffd5

Please sign in to comment.