Skip to content

Commit

Permalink
Fix doc links (#429)
Browse files Browse the repository at this point in the history
  • Loading branch information
timholy committed Sep 14, 2020
1 parent e176da8 commit 583de6c
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion docs/src/ast.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ The key advantage of lowered representation is that it is fairly well circumscri
- Names are fully resolved by module
- Macros are expanded

[Julia AST](https://docs.julialang.org/en/latest/devdocs/ast/) describes the kinds of
[Julia AST](https://docs.julialang.org/en/v1/devdocs/ast/) describes the kinds of
objects that can appear in lowered code.

Let's start with a demonstration on a simple function:
Expand Down
2 changes: 1 addition & 1 deletion docs/src/internals.md
Original file line number Diff line number Diff line change
Expand Up @@ -167,7 +167,7 @@ Test Passed
Code that defines new `struct`s, new methods, or new modules is a bit more complicated
and requires special handling. In such cases, calling `finish_and_return!` on a frame that
defines these new objects and then calls them can trigger a
[world age error](https://docs.julialang.org/en/latest/manual/methods/#Redefining-Methods-1),
[world age error](https://docs.julialang.org/en/v1/manual/methods/#Redefining-Methods-1),
in which the method is considered to be too new to be run by the currently compiled code.
While one can resolve this by using `Base.invokelatest`, we'd have to use that strategy
throughout the entire package. This would cause a major reduction in performance.
Expand Down

0 comments on commit 583de6c

Please sign in to comment.