John Ericson b9dce11712 lib: Make overrideScope' which takes arguments in the conventional order ... The `overrideScope` bound by `makeScope` (via special `callPackage`) took an override in the form `super: self { … }`. But this is dangerously close to the `self: super { … }` form used by *everything* else, even other definitions of `overrideScope`! Since that implementation did not even share any code either until I changed it recently in 3cf43547f4, this inconsistency is almost certainly an oversight and not intentional. Unfortunately, just as the inconstency is hard to debug if one just assumes the conventional order, any sudden fix would break existing overrides in the same hard-to-debug way. So instead of changing the definition a new `overrideScope'` with the conventional order is added, and old `overrideScope` deprecated with a warning saying to use `overrideScope'` instead. That will hopefully get people to stop using `overrideScope`, freeing our hand to change or remove it in the future.		2018-09-24 17:50:11 -04:00
..
buffer.nix
elpa2nix.el
elpa.nix
generic.nix
melpa2nix.el
melpa.nix	Fix pname to ename propagation if null	2018-07-27 08:15:46 +02:00
setup-hook.sh
trivial.nix
wrapper.nix	lib: Make overrideScope' which takes arguments in the conventional order	2018-09-24 17:50:11 -04:00