libera/#commonlisp - IRC Chatlog
Search
17:10:06
beach
The dictionary entry for the declaration OPTIMIZE says that the consequences are unspecified if a quality appears more than once with different values. But what if such a quality appears once in each of two different consecutive declarations in the same form?
17:11:29
beach
Also, a (nother) WSCL issue: The dictionary entry for the declaration DECLARATION uses the term "declaration name", but I think it should be "declaration identifier". No?
17:13:57
beach
The dictionary entry for the declaration TYPE also uses "name of a declaration" and "declaration name".
17:36:25
jcowan
beach: I don't think consecutiveness matters, so presumably the later declaration wins; the effective scope of the earlier declaration just happens to be empty.
17:38:20
jcowan
So you are saying the scope of a global declaration is the whole program, or the current file, or what?
17:41:31
jcowan
Proclamations are defined as global declarations, so by "declarations" here you mean local declarations?
17:42:53
jcowan
Unfortunately 3.3.4 is silent as to the scope of declarations that aren't bindings, unless I am misreading it.
17:49:45
skin
http://www.lispworks.com/documentation/lw50/LWUG/html/lwuser-90.htm#:~:text=There%20are%20two%20distinct%20uses%20of%20declare%2C%20one,code%20faster%2C%20or%20with%20more%20sophisticated%20debugging%20options.
17:53:02
pjb
(macroexpand-1 '(declaim (optimize (speed 1)))) #| --> (progn (eval-when (:compile-toplevel) (ccl::compile-time-proclamation '((optimize (speed 1))) nil)) (eval-when (:load-toplevel :execute) (proclaim '(optimize (speed 1))))) ; t |#
17:53:56
jackdaniel
afair the implementation may treat declaim as file-local compilation declamation
17:54:10
jackdaniel
i.e after compiling the file the declaration does not stay in the global environment
17:55:23
pjb
So, one more reason not to use proclaim (even in an eval-when). You definitely don't want a compiled file to change your declarations…
21:22:33
White_Flame
when a customer wants a program to do X, and just wants it invoked by whatever their devops does, regardless of language implemented
1:04:16
cpli
how do i include trivial-features in my project such that i can `error` on certain trivial features?
3:13:22
loke[m]
@cpli:libera.chat: you just add it to the dependencies in the asd file, or am I miunderstanding the question?
4:00:05
jmercouris
are you trying to actually literally call something from the trivial features system in your asd?
4:12:35
bitblit1
<jmercouris> "are you trying to actually..." <- I think that is what he was trying to do.
4:13:29
jmercouris
then you have a couple of options, basically you can require it, embed it in the top of your asd and use it