inappropriate unused_binding diagnostic with named attribute set argument (@) · Issue #73 · oxalica/nil · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a general issue, but the common use-case where I'm hitting it is in a flake when utilizing the registry to avoid specifying an explicit input URL:
inputs.nixos-hardware is not used directly in the function body, but in an expression in an included file which is passed inputs (same for home-manager and helix (src). Basically, since nil doesn't analyze into included files, it should be enough if the named attribute set argument (here, inputs) is referenced in the function body. Does that make sense?
Also, thank you so much for working on nil. It has greatly improved my daily experience of working on Nix code, and with each new analysis feature it gets better. ❤️
The text was updated successfully, but these errors were encountered:
Confirmed fixed with flake inputs. I do feel like this could still be an issue in general with named attrset arguments that get passed into a function defined elsewhere, but I don't have a specific instance in mind so I'm happy with this.
This is a general issue, but the common use-case where I'm hitting it is in a flake when utilizing the registry to avoid specifying an explicit input URL:
inputs.nixos-hardware is not used directly in the function body, but in an expression in an included file which is passed
inputs
(same forhome-manager
andhelix
(src). Basically, since nil doesn't analyze into included files, it should be enough if the named attribute set argument (here, inputs) is referenced in the function body. Does that make sense?Also, thank you so much for working on nil. It has greatly improved my daily experience of working on Nix code, and with each new analysis feature it gets better. ❤️
The text was updated successfully, but these errors were encountered: