-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provenance, aka “where did this attribute come from” #235
Comments
This wouldn't be hard to do I think, using metavalues to store this information, without much overhead. Then the
As a side note, I don't see a way of interpreting this other than an infinite loop, but I get what you meant. |
Ah yes, `self` would refer to the `foo` I just define in this case, so I
guess it would have to be `super` or something?
…On Fri, Dec 4, 2020 at 1:41 PM Yann Hamdaoui ***@***.***> wrote:
This wouldn't be hard to do I think, using metavalues to store this
information, without much overhead. Then the query sub-command could show
this information along the value.
(import A) & { foo = self.foo + 10 }
As a side note, I don't see a way of interpreting this other than an
infinite loop, but I get what you meant.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#235 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYB5ZRIMY3P67RAWPAY2RLSTDKHBANCNFSM4ULRIACA>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One use-case for nixpkgs overlays I just had: We define an overlay of pkgs where we override and add some packages.
I just went directly to nixpkgs to see the definition of a package, totally missing that we had overridden it locally.
It would be nice if there was a “stack trace” of sorts that can show how attributes “came to be”, aka where they were added/changed. I don’t know how feasable that is.
So, for example, file A defines:
file B says:
And if I tell nickel: “show me the provenance of
foo
inB
”:or somesuch.
This uses the proposed
self
feature to do self-recursion with merges, but of course could be adapted to other ways of recursion.The text was updated successfully, but these errors were encountered: