7:05:47axionI'm working on extending my doubly linked list data structure implementation, as it was pretty naive. I'm encountering some interesting hurdles with the optimization I employed.
7:15:30beachwhoman: What is a "procedurally generated language"?
7:22:14jackdanielhscl reminds me boringcc principles: https://groups.google.com/forum/m/#!msg/boring-crypto/48qa1kWignU/o8GGp2K1DAAJ
7:22:59jackdanielanother approach, which is fully standard compatible would be signalling conditions whenever programmer tries to depend on undefined / underspecified mechanism
7:23:33jackdanielbecause if it's undefined, compiler is free to signal an error
7:23:37beachWell, I am planning to be very careful not to degrade performance.
7:24:57beachThat might mean leaving it unspecified when safety is 0 and not otherwise.
7:25:39beachBut yes, if there is no reasonable action to take, then signaling an error is an option.
7:46:21azrazaleaThis is what I ended up with https://gitlab.com/azrazalea/azrazalea-net/blob/master/functions.lisp
7:46:32azrazaleaWith the addition of https://gitlab.com/azrazalea/coleslaw/commit/577053276c87833bd2419e9928d5924b6c655a68 to coleslaw
8:19:58jack_rabbitHow do common lisps deal with infinitely recursive macro expansions? They obviously can't fully expand them at compile-time.
8:22:09jack_rabbitbut doing further expansion at runtime inside a compiled function seems like it would require modifying a compiled function on the fly.
8:23:04beachjack_rabbit: Macro expansion is defined to be done at compile time.
8:23:15beachSo you can't have infinitely recursive macros.
8:27:07jack_rabbitaha. okay, so when I enter that and evaluate (foo (1)) at the repl, it works. Trying to compile a file with it fails with blown stack, as I would have expected.
8:28:51jack_rabbitI was just surprised it worked in the repl. Guess it doesn't do full expansion when it's interpreting.
8:32:54edgar-rftjack_rabbit: an infinite stack is an inevitable requirement for infinite recursion, infinite compile-time will be next ... :-)
8:36:29jack_rabbitI know it can't *actually* recur infinitely, but if you expand only as necessary you can still evaluate a form.
8:43:09edgar-rftIf your macro non-recursively expands into a recursive helper-function or a LABELS form you can implement run-time checks for the recursion depth.
13:57:32proleMy distro repositorie purpose a version of slime, slime-2.15, but it don't work either, with the error saying that I need make operation, and just stopping on a file
14:01:46proleThat's crazy how the help is good here. I truly don't understand why people are saying that the lisp community is bad; I only met very good and helpful people here
14:03:08beachprole: Yes, if you have reasonable questions, you follow the advice you get, and you learn between two questions, then usually the answers are to the point.
18:56:54drmeisterHi - I added some specialized vector/array types to Clasp and I thought I did everything right - but the new types/classes aren't working properly wrt subtypep
18:58:01drmeisterUh - pausing while I formulate thought