mirror of
https://github.com/ilyakooo0/nixpkgs.git
synced 2024-11-15 13:37:21 +03:00
60e8fcf0e5
The explicit remove helped to uncover some hidden uses of `optionSet` in NixOps. However it makes life harder for end-users of NixOps - it will be impossible to deploy 19.03 systems with old NixOps, but there is no new release of NixOps with `optionSet` fixes. Also, "deprecation" process isn't well defined. Even that `optionSet` was declared "deprecated" for many years, it was never announced. Hence, I leave "deprecation" announce. Then, 3 releases after announce, we can announce removal of this feature. This type has to be removed, not `throw`-ed in runtime, because it makes some perfectly fine code to fail. For example: ``` $ nix-instantiate --eval -E '(import <nixpkgs/lib>).types' --strict trace: `types.list` is deprecated; use `types.listOf` instead error: types.optionSet is deprecated; use types.submodule instead (use '--show-trace' to show detailed location information) ``` |
||
|---|---|---|
| .. | ||
| systems | ||
| tests | ||
| asserts.nix | ||
| attrsets.nix | ||
| customisation.nix | ||
| debug.nix | ||
| default.nix | ||
| deprecated.nix | ||
| fetchers.nix | ||
| filesystem.nix | ||
| fixed-points.nix | ||
| generators.nix | ||
| kernel.nix | ||
| licenses.nix | ||
| lists.nix | ||
| meta.nix | ||
| minver.nix | ||
| modules.nix | ||
| options.nix | ||
| sources.nix | ||
| strings-with-deps.nix | ||
| strings.nix | ||
| trivial.nix | ||
| types.nix | ||
| versions.nix | ||
| zip-int-bits.nix | ||