From 8d7200d9f36ca01ea0d9d08bb510b06139cf4e6a Mon Sep 17 00:00:00 2001 From: Wolfgang Walther Date: Thu, 30 Oct 2025 19:22:57 +0100 Subject: [PATCH] aliases: remove hacky workaround for warnings on strings This causes confusing eval errors when not using these values (here: `system`) in a string interpolation context. The change will potentially be noisy for nix search. If we want a deprecation period for this attribute instead of just throwing immediately, we will have to accept this, at least temporarily. --- pkgs/top-level/aliases.nix | 5 ----- 1 file changed, 5 deletions(-) diff --git a/pkgs/top-level/aliases.nix b/pkgs/top-level/aliases.nix index a11d2bb9e8c7..c18ed414a063 100644 --- a/pkgs/top-level/aliases.nix +++ b/pkgs/top-level/aliases.nix @@ -230,11 +230,6 @@ let arg: lib.warn msg (v arg) else if lib.isList v then map (lib.warn msg) v - else if lib.isString v then - # Unlike the other cases, this changes the type of the value and - # is therefore a breaking change for some code, but it’s the best - # we can do. - { __toString = lib.warn msg (lib.const v); } else # Can’t do better than this, and a `throw` would be more # disruptive for users…