Search
Wednesday, 19th of January 2022, 3:09:12 UTC
13:20:18
luis`
sveit: did you know stassats has a Patreon page? ;-)
13:40:31
phoe
Krystof: AFAIK SBCL at some point in time had a compile-time warning for things like (defstruct foo (x 0 :type string)) - do you know if I remember correctly and what happened to it?
13:41:05
Krystof
you do remember correctly
13:41:48
Krystof
I can't remember when it got removed. (I think it was unintentionally, as a side-effect of something else)
13:45:01
phoe
do you remember when it got introduced?
13:45:08
phoe
I am trying to look at the SBCL release notes
13:45:32
phoe
1.5.9 mentions: enhancements: more thorough compile-time type checking of various initforms (defclass, &key, defstruct).
13:45:40
phoe
but I can't get that warning when compile-file'ing on that version
14:09:59
phoe
does anyone have any pointers related to that one?
14:10:15
phoe
I'd ask Stas but he isn't around at the moment; he usually reads chat logs though
14:20:52
stassats
phoe: it has never been released
14:21:50
phoe
so I actually misremembered
14:22:09
phoe
why has it never been released? backwards compatibility?
14:22:15
phoe
is the code available anywhere?
14:22:23
stassats
some people like to put bad things there
14:23:15
phoe
in the initform? yes, sounds like a good reason to issue warnings because of that
14:24:16
Shinmera
Warnings break quicklisp
14:24:26
Shinmera
And I assume too many things would have broken?
14:25:09
stassats
phoe: no, they like doing that on purpose
14:25:12
phoe
I mean, it's not the first time SBCL would issue type warnings that broke already broken code
14:25:15
phoe
example being https://github.com/AccelerationNet/access/commit/cadf09373da4afc739cf177d0fcea3612778a3f7
14:25:40
phoe
where SBCL started noticing that (APPLY '(SETF AREF) ...) is bad at compile time
14:30:54
phoe
also, is the code for that available anywhere?
Wednesday, 19th of January 2022, 15:09:12 UTC