@@ -27,7 +27,7 @@ defmodule Mix.Tasks.Xref do
27
27
touching one file in a project causes a large subset of the project
28
28
to recompile. The most common cause of these problems are the so-called
29
29
"compile-connected" files. Those are files you depend on at compile-time
30
- (for example, by invoking its macro or using it in the body of amodule )
30
+ (for example, by invoking its macro or using it in the body of a module )
31
31
which also have their own dependencies.
32
32
33
33
Therefore, if your goal is to reduce recompilations, the first step is to run:
@@ -61,8 +61,8 @@ defmodule Mix.Tasks.Xref do
61
61
because compile time dependencies are transitive.
62
62
63
63
Having compile time dependencies is a common feature in Elixir projects.
64
- However, the modules you depend on at compile-time must avoid runtime
65
- dependencies within the same project. You can understand all of the
64
+ However, the modules you depend on at compile-time must avoid dependencies
65
+ to modules within the same project. You can understand all of the
66
66
dependencies of a given file by running:
67
67
68
68
$ mix xref trace lib/livebook_web.ex
@@ -75,7 +75,7 @@ defmodule Mix.Tasks.Xref do
75
75
Elixir tracks three types of dependencies between modules: compile,
76
76
exports, and runtime. If a module has a compile time dependency on
77
77
another module, the caller module has to be recompiled whenever the
78
- callee changes (or any runtime dependency of the callee changes).
78
+ callee changes (or any dependency of the callee changes).
79
79
Let's see an example:
80
80
81
81
# lib/a.ex
0 commit comments