Don't require ellipsis in NixOS module definitions.

lib/modules.nix

@@ -13,6 +13,7 @@ let
     elem
     filter
     foldl'
+    functionArgs
     getAttrFromPath
     head
     id
@@ -510,7 +511,7 @@ let
       # context on the explicit arguments of "args" too. This update
       # operator is used to make the "args@{ ... }: with args.lib;" notation
       # works.
-    in f (args // extraArgs);
+    in f (builtins.intersectAttrs (functionArgs f) (args // extraArgs));
 
   /* Merge a list of modules.  This will recurse over the option
      declarations in all modules, combining them into a single set.

lib/tests/modules.sh

@@ -433,6 +433,9 @@ checkConfigError 'Could not load a value as a module, because it is of type "fla
 checkConfigOutput '^true$' "$@" config.enable ./declare-enable.nix ./define-enable-with-top-level-mkIf.nix
 checkConfigError 'Could not load a value as a module, because it is of type "configuration", in file .*/import-configuration.nix.*please only import the modules that make up the configuration.*' config ./import-configuration.nix
 
+checkConfigOutput '"foo"' config.foo ./no-ellipsis-module.nix
+checkConfigOutput '"foo"' config.foo ./module-with-at-pattern.nix
+
 # doRename works when `warnings` does not exist.
 checkConfigOutput '^1234$' config.c.d.e ./doRename-basic.nix
 # doRename adds a warning.

lib/tests/modules/module-with-at-pattern.nix

@@ -0,0 +1,5 @@
+# this no longer works since functionArgs is blind to both `...` and `@`-patterns
+{ ... }@inputs: {
+  options.foo = inputs.lib.mkOption { type = inputs.lib.types.str; };
+  config.foo = "foo";
+}

lib/tests/modules/no-ellipsis-module.nix

@@ -0,0 +1,5 @@
+# the module can now request only what it needs without a `...`.
+{ lib }: {
+  options.foo = lib.mkOption { type = lib.types.str; };
+  config.foo = "foo";
+}