elastic-arm-3e34f16b: building 5wcnsbxndhnjl9vaimixzn8gliw1mxf2-iets-ast-grep.drv
error[no-function-level-use]: move this `use` to the top of the module
    ┌─ tests/pure.rs:210:5
    │  
209 │ ╭ fn linked() -> TempDir {
210 │ │     use std::os::unix::fs::symlink;
    │ │     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    · │
223 │ │ }
    │ ╰─'

error[no-inline-absolute-paths]: use a `use` import instead of an inline crate::/super::/std:: path
    ┌─ src/builtins/store_hooks.rs:261:16
    │
261 │     let path = crate::compile::canon_path(path);
    │                ^^^^^^^^^^^^^^^^^^^^^^^^^^

error[no-comment-essays]: comment block of 8+ lines; condense it to the WHY
    ┌─ src/builtins/store_hooks.rs:191:1
    │                  
184 │     ╭             /// the path resolution ended at, and its place in the (virtual) store, `None`
185 │     │ ╭           /// for one the real file system answers. [`resolve_links`] runs under a store
    │     ╰────────────'
186 │       │ ╭         /// path this evaluation copied from a local tree, and in a pure evaluation
    │       ╰──────────'
187 │         │ ╭       /// under the project: there the kernel would follow a link out of the allow
    │         ╰────────'
188 │           │ ╭     /// list, which is judged on the text of the path. A fetched input's spool
    │           ╰──────'
189 │             │ ╭   /// resolves a member's links inside the entry itself, and elsewhere the
    │             ╰────'
190 │               │ ╭ /// kernel resolves as the accessor would, so the walk is skipped and this
    │               ╰──'
191 │ ╭               │ /// costs the one lookup the reader needed anyway.
    │ │               ╰'
192 │ │ ╭               pub fn located(
    │ ╰────────────────^
    ·   │              
217 │   │               }
    │   ╰───────────────'

Error: 3 error(s) found in code.
Help: Scan succeeded and found error level diagnostics in the codebase.