|
4023 | 4023 |
|
4024 | 4024 | (defn- flycheck-evaluator |
4025 | 4025 | `` |
4026 | | - An evaluator function that is passed to `run-context` that lints (flychecks) code for `flycheck`. |
4027 | | - This means code will parsed and compiled, macros expanded, but the code will not be evaluated. |
| 4026 | + An evaluator function that is passed to `run-context` that lints |
| 4027 | + (flychecks) code for `flycheck`. This means code will be parsed, |
| 4028 | + compiled, and have macros expanded, but the code will not be |
| 4029 | + evaluated. |
4028 | 4030 | `` |
4029 | 4031 | [thunk source env where] |
4030 | 4032 | (when (and (tuple? source) (= (tuple/type source) :parens)) |
|
4041 | 4043 |
|
4042 | 4044 | (defn flycheck |
4043 | 4045 | ``` |
4044 | | - Check a file for errors without running the file. Found errors will be printed to stderr |
4045 | | - in the usual format. Top level functions and macros that have the metadata `:flycheck` will |
4046 | | - also be evaluated during flychecking. For full control, The `flycheck` metadata can also be a function |
4047 | | - the takes 4 arguments - `thunk`, `source`, `env`, and `where`, the same as the `:evaluator` argument to `run-context`. |
| 4046 | + Check a file for errors without running the file. Found errors |
| 4047 | + will be printed to stderr in the usual format. Top level functions |
| 4048 | + and macros that have the metadata `:flycheck` will also be evaluated |
| 4049 | + during flychecking. For full control, the `:flycheck` metadata can |
| 4050 | + also be a function that takes 4 arguments - `thunk`, `source`, `env`, |
| 4051 | + and `where`, the same as the `:evaluator` argument to `run-context`. |
4048 | 4052 | Other arguments to `flycheck` are the same as `dofile`. Returns nil. |
4049 | 4053 | ``` |
4050 | 4054 | [path &keys kwargs] |
|
0 commit comments