Search
Tuesday, 11th of June 2019, 21:39:18 UTC
21:39:18
dagg
Why this feature is so commonly used, if it makes code so unflexible, I wonder.
21:39:40
dagg
Instead of the approach normal for Scheme (or Emacs Lisp): (setf a (or a 0)), I mean.
21:39:42
Bike
i think there is actually a bias against &optional in new code. maybe only a little, though.
21:40:01
Bike
functions sometimes do that too.
21:40:15
Bike
like a lot of the standard printing functions.
21:41:01
pjb
remexre: https://pastebin.com/grqu04NG
21:42:40
pjb
remexre: https://pastebin.com/QwTqpYzL
21:45:16
remexre
pjb: huh, okay, I'll give those a look in a bit; thanks!
21:46:15
pjb
remexre: now of course, if you have a lot of methods, you may want to be more efficient in find-predicate-dispatch-method. eg. you can use a tree instead of a list. or a tree of hash-tables, etc.
22:05:42
didi
Curious limitation: the size of a byte is unchangeable after the stream has been created.
22:06:09
didi
Not that I ever had to use a byte size different than 8.
2:53:24
beach
Good morning everyone!
5:01:14
hatchback17645
(find-all-symbols store-here)
5:13:19
beach
hatchback17645: Are you new here?
7:22:16
sindan
Is there a way for a function to access the call stack without calling up the debugger?
7:23:03
jackdaniel
sindan: try trivial-backtrace library
7:23:21
jackdaniel
there are also some bits for that in swank, but you'd need to look into it yourself
7:23:42
jackdaniel
I think that someone made yet another library for that but I can't recall the name nor the author
7:25:10
sindan
trivial-backtrace is all I need
9:37:59
adlai
didi: there are peek-char and peek-byte that unread by default, if your usecase is likely to need this unfeature more often than not
9:38:47
adlai
e.g., if you're reading a code which is mostly multibytes, and occasionally a single byte.
Wednesday, 12th of June 2019, 9:39:18 UTC