libera/#commonlisp - IRC Chatlog

3:09:02 char Hey bike, is this a good place to talk about ctype stuff? I would like there to be some concept of aliasing (as in deftype). Using the string type as an example, it gets really ugly after parsing, then unparsing. Would you be open to a parsed ctype retaining what its original form was perhaps? Obviously if enough operations take place then the alias will no longer apply.

3:49:49 bike char: might as well talk about it here. i already put in a ton of logic to try to unparse the types to something nice, but yeah, might be easier to just keep around the original if only for display.

3:50:07 bike and then fall back to the unparse logic if the type was made artificially by whatever means

3:51:39 char As someone who now understands the type system and ctype. I appreciate the expansion of the string type for example. As someone who just wants to string, I don't want to see a huge disjunction type.

3:51:50 bike naturally

3:52:35 bike the unparse method on disjunctions is more code than the entire rest of the type's implementation. lol.

3:55:18 char I'm hoping to take advantage of user defined type aliases as well.

3:57:00 bike i'm not sure exactly what you mean by that. the idea is that deftype is handled by typexpand.

6:25:20 char I'm just giving another example use case.

8:29:46 xaltsc ** NICK Guest3399

8:30:39 Guest3399 ** NICK xaltsc

10:29:05 thuna` ::clhs READ-PERSERVING-WHITESPACE

10:29:05 Colleen "READ-PERSERVING-WHITESPACE" not found in CLHS.

10:29:12 thuna` ::clhs READ-PRESERVING-WHITESPACE

10:29:12 Colleen Read-preserving-whitespace http://www.lispworks.com/reference/HyperSpec/Body/f_rd_rd.htm

10:29:42 thuna` In the third paragraph in the description, the second READ is a typo for READ-PRESERVING-WHITESPACE, correct?

12:15:40 beach Looks that way.

12:15:56 beach thuna`: Would you care to submit a WSCL issue?

12:36:40 thuna` sure

12:36:56 beach Thanks.

13:16:07 Shinmera really hate that DESCRIBE does not return the described object

13:24:26 jackdaniel why?

13:25:11 Shinmera because it means I can't just carry on probing the object with *, I have to do **, and if I describe it again and again with ** and *** I end up losing access to it altogether

13:25:23 Shinmera So I keep having to do the spiel of first typing ** to get it into * and then describing again and aaaaa

13:25:40 Shinmera and no I don't want to stuff it into a variable

13:25:58 Shinmera it's just kinda dumb there's no reason for it to return no values, just give me the object back

13:29:00 Shinmera anyway, I can hack it in my init file, just a thing

13:30:07 yitzi Perlis intervened and demanded that DESCRIBE not know the value of anything.