Index: TODO
===================================================================
diff -u -N -rbdf624ecd1bb56b2036b2affe95b0fed1a672a59 -r03bb3de2057c1604e00eaefd70b84975d3c816fe
--- TODO	(.../TODO)	(revision bdf624ecd1bb56b2036b2affe95b0fed1a672a59)
+++ TODO	(.../TODO)	(revision 03bb3de2057c1604e00eaefd70b84975d3c816fe)
@@ -5934,6 +5934,19 @@
 ========================================================================
 TODO:
 
+- nsf::parseargs would need some more love:
+  * what is the intended behavior, in these edge cases?
+
+   # TODO: Are the below cases intended?
+    ? {apply {{} {nsf::parseargs {a} {}; llength [info vars];}}} 0
+    ? {apply {{} {nsf::parseargs {} {1}; llength [info vars];}}} 0
+
+  Right now, parseargs is more or less a NOOP in these cases (which is
+  not consistent with arg-handling otherwise).
+
+  * Should the behavior in the Tcl-only case be more like [lassign] or
+    procedure-like record checking?
+    
 - Refactor: on the property/variable-creation paths,
   parseParameterSpec is currently called twice. once before
   createFromParameterSpec, once within. This should not be needed.  -