11:06:16jmercourissomehow deleting the key argument in request-resource-block causes the error to go away
11:06:19jmercouristhis is what makes no sense to me
11:08:09jmercourishow can a key argument to a function cause a name conflict?
11:25:17trocado(rename-file #p"test/current/" #p"test/123/") is saying it can't rename [current dir]/test/current/ to [current dir]/test/current/test/123/
11:28:30Xachtrocado: RENAME merges the new with the old
11:28:45Shinmera"The primary value, defaulted-new-name, is the resulting name which is composed of new-name with any missing components filled in by performing a merge-pathnames operation using filespec as the defaults."
11:28:45Xachtrocado: if you don't want that, make sure the new name is more complete
11:29:54Xachi think this is widely unexpected behavior, but it does allow some shortcuts if you have it memorized. like (rename-file "/My/cool/file/frob.lisp" "frob-backup") => "/My/cool/file/frob-backup.lisp"
11:32:24Xachit has internal logic at least. the problem with intuition and expectation is it's formed by whatever you learn first, and i learned a different style first (unix mv style).
14:25:53srandon111guys what is meant by "natural recursion"? and what would it be a "non-natural recursioN" ? i found a post on stackoverflow but wasn't able to understand still
14:29:36_deathlooks like an idiosyncratic term to me
14:30:31dloweyeah, I would interpret as "solving a problem particularly amenable to recursion" but it's not a term of art
14:30:33Bikerecursion on natural numbers? no, i've never heard this term either
14:38:05phoeit seems to be related to natural numbers, and the most natural operations on these: a check whether a number is zero, adding one to a number, subtracting one from a number
14:38:19Bikeoh, like a natural transformation maybe?