freenode/#lisp - IRC Chatlog
Search
5:38:04
beach
p_l: Yes, thanks. Monday mornings are always chaotic around here. This one a bit more than usual. But it is all planned and under control. You?
5:40:52
p_l
patrixl: I don't believe it will happen to me before retirement, and I expect retirement to come maybe ~20 years after I'm dead
6:20:09
aeth
From HN 2 weeks ago... "Is Death Reversible?" https://news.ycombinator.com/item?id=21409744
6:20:21
aeth
That means that in the future, your employer will revive you from death so you can keep working!
7:01:50
p_l
patrixl: *after* my death. what isn't clear is whether I'd be still working, certainly I won't get to enjoy retirement
7:26:11
flip214
p_l: obviously you need to enjoy working, then it doesn't matter whether you retire or not
7:28:01
flip214
well, in 18 years you'll be one of the long-sought experts for the 2038 unix date migration, perhaps that's sufficient to let you retire
7:32:37
White_Flame
or dig into the hashtable internals of your implementation, and you'll likely find arrays to index into randomly
11:54:40
many-questions
When I step in slime, SLDB, emacs momentarily flashes a yellow highlight to show which form is being evaluated. Is there a way to make this flash longer, or even have a permanent highlight of the current form?
12:12:34
Xach
many-questions: that's an interesting question. i couldn't figure it out quickly from slime.el, but it can't be too tricky.
12:17:08
trittweiler
many-questions, There does not seem a way right now to configure this. To change the source code, you would want pass in a third parameter to slime-flash-region in slime-highlight-sexp
12:20:24
trittweiler
From an UI point of view, perhaps what should be done is to add a command that redoes the last flash.
12:31:41
Xach
trittweiler: can you tell me how sldb-step ties in to slime-highlight-sexp? I couldn't see the call sequence.
12:38:42
phoe
If a Common Lisp type is non-NIL and non-T, then can/should negating it ever produce a NIL or T type?
12:39:33
phoe
Set theory tells me that this should never be the case, since a negation of a non-empty/non-universe set is never an universe/empty set.
12:46:06
phoe
(NOT (OR (NOT INTEGER) (REAL (-0.5D0)) (REAL * (-0.5D0)))) is the smallest actual test case I've found that produces a NIL ctype on CCL and SBCL.
12:55:06
phoe
So this also must mean that (OR (NOT INTEGER) (INTEGER * -1) (REAL (-3.5D0)) (REAL * (-3.5D0))) is T.
12:55:36
phoe
And that (OR (NOT INTEGER) (INTEGER * -1) (REAL (-3.926510009989861D+7)) (REAL * (-3.926510009989861D+7))) is T.
13:26:24
trittweiler
Xach: grep for :show-frame-source in the *.el and *.lisp files. The control flow is not very apparent at all, you are right
13:27:47
phoe
First, somehow improve the type parsing, so CCL/SBCL can infer from the above type that it is equivalent to T.
13:28:19
phoe
Second, try and figure out why the hell (VALUES NIL T) is returned, which means that SBCL/CCL are *sure* that their decision is correct even if it is not.
15:42:33
pjb
phoe: it depends on whether "type-designator-1 IS type-designator-2" means the two type designators are identical, or whether they represent the same type, ie. the same set of values?
15:43:40
pjb
phoe: specifically, (and (not (equalp '(and (eql 1) (eql 2)) 'nil)) (subtypep '(and (eql 1) (eql 2)) 'nil) (subtypep 'nil '(and (eql 1) (eql 2)))) #| --> t ; t |#
15:44:03
pjb
phoe: but implementations may not be able to determine the subtype relationship in all cases!
15:45:23
pjb
eg. (defun always-nil (x) 'nil) (deftype few () '(satisfies aways-nil)) (and (subtypep 'always-nil 'nil) (subtypep 'nil 'always-nil)) #| --> nil |#
15:46:42
phoe
pjb: if the implementation is unable to determine the relationship, it must return NIL NIL.
15:52:16
jeosol
getting this sbcl specific error: dynamic space too small for core: 1912160KiB required, 1048576KiB available.
15:52:51
jeosol
when I try to load a core through slime. Works on the shell no issues. I do have a lot memory not used when I checked with top (~27GB)
16:04:19
phoe
I'll show you the commit when I'm done. Maybe SBCL has a similar place and you will be able to port it to SBCL.
16:18:52
phoe
https://github.com/phoe-trash/ccl/commit/ba281521b1cfbffe3c3b6ef0a56e27e425438f72?ts=8
16:22:21
easye
ACTION is really digging Travis with ABCL <https://travis-ci.org/easye/abcl/builds/613579263>
16:24:23
easye
As a public service, the Common Lisp Foundation also has Gitlab CI available to all users.
16:26:03
phoe
Travis has builds on macOS/Windows/Linux for free on github. Sourcehut has Linux/BSDs.
16:28:08
easye
"Correct under Linux means the vendors have the responsibility to make it work on their commercial offering."
16:28:53
easye
" maybe they can't get any CI utils to run on catalina": it's gonna take a little elbow grease, but they have the engineering talent and time to do it.