freenode/#lisp - IRC Chatlog
Search
7:45:06
phoe
vector-pop will work well, but it will not reallocate the vector if the fill pointer is small compared to the vector length
7:47:36
asarch
"4While frequently used together, the :fill-pointer and :adjustable arguments are independent--you can make an adjustable array without a fill pointer. However, you can use VECTOR-PUSH and VECTOR-POP only with vectors that have a fill pointer and VECTOR-PUSH-EXTEND only with vectors that have a fill pointer and are adjustable. You can also use the function ADJUST-ARRAY to modify adjustable arrays in a variety of ways beyond just extending the length of a
7:47:56
asarch
This link?: http://www.lispworks.com/documentation/HyperSpec/Body/f_vec_po.htm#vector-pop
7:49:25
beach
asarch: It is essential that you start trying to interpret Common Lisp HyperSpec dictionary entries, so that you can look things up yourself.
7:49:26
asarch
I know, I know. I just I thought that I would need some other "special" function to pop a vector that has been vector-push-extended
7:50:22
beach
asarch: And, don't you think such a function would be present in the dictionary entry on VECTOR-PUSH-EXTEND?
7:57:27
flip214
beach: sorry, I thought that was the way to get a URL to a CLHS page. Seems I remembered wrong.
8:01:01
specbot
set-funcallable-instance-function: http://metamodular.com/CLOS-MOP/set-funcallable-instance-function.html
11:57:52
selwyn
heisig: do you use maxima as part of your research? either together with petalisp or separately
12:02:53
heisig
selwyn: I have used maxima in two previous projects, but I don't use it for Petalisp.
12:06:02
heisig
Some of my colleagues use SymPy, but it is so slow and full of bugs that I'm tempted to write an alternative based on cl4py and maxima.
12:09:58
heisig
beach: Climaxima looks very promising. But my colleagues want a computer algebra system with Python bindings.
12:12:02
flip214
heisig: perhaps putting effort into https://github.com/pinterface/burgled-batteries would be more interesting?
12:14:32
heisig
flip214: burgled-batteries is about using Python code from Lisp (a horrible thought!). What I want to achieve with cl4py is that one can use Lisp code from Python.
12:15:24
flip214
well, why not provide them an interface "load python file" in climaxima instead? Or have a text REPL for them?
12:20:17
selwyn
given the intention that python programmers should be able to play around with code written in lisp, i suspect that the best approach is to have lisp available from the (c)python REPL, if only to make it more attractive at first sight
12:20:42
selwyn
(as opposed to a FFI approach, or having a python implementation written in Common Lisp)
12:22:15
selwyn
this question does not have a cut and dried answer, since it depends on reasoning about other people's prejudices concerning choosing different software libraries
12:23:29
selwyn
one thing i do notice: most enthusiastic python programmers would not like to program in something other than CPython as that implementation contains the bulk of the libraries that make scientific computation feasible (iiuc)
12:26:21
flip214
still, I would see it as a kind of responsibility to gently nudge them to saner programming languages ... ;)
12:26:27
selwyn
i have not used burgled batteries, but i again suspect that in order to use it practically, one would need to make it aware of which of the various python binaries and environments it should use on a given system.. this seems like a lot of work
12:27:45
selwyn
flip214: well, this is one of my hopes from cl4py. unfortunately, it did not arouse immediate interest from some pythonistas i know
12:30:49
selwyn
they said that there's no point given the range of things they can do with python. it's understandable - most people will not experiment with new things if they are happy with what they have. it's a different matter if some new library, such as a 'python-maxima' were to be presented
12:36:13
heisig
selwyn: That is good to know. One thing that might interest pythonistas already is having access to cl:compile (and cl:disassemble).
12:42:24
selwyn
i have noticed some frustration at the reality of having to switch over to C to write performant code for python
12:43:30
selwyn
heisig: anyway, i ask since i am thinking of using maxima for some symbolic manipulation of n-dimensional tensors and matrices
12:45:16
heisig
selwyn: I haven't used maxima for tensor manipulation yet. But there seem to be some modules for it.
12:49:47
guicho
Hi all, last week I presented my numpy-clone in common lisp in Shibuya.lisp meetup. The talk was in Japanese but here is the youtube link to the recording which starts right at the beginning of the demo on the REPL, which you could understand. https://youtu.be/dWfR25EZNjs?t=6259
12:56:18
flip214
why not enter mostly-python-syntax in a text field in clmaxima, convert that to CL (shown in a second field) and then run that?
13:00:25
guicho
heisig: I basically reimplemented a specialized version of type inference mechanism. Currently every inference happens in the runtime, but they will be shifted to the compile time in the future.
13:02:39
guicho
heisig: specialized because it needs to account for the type upgrading in the common lisp array. Ratios are all converted to single-floats. Bignums are truncated to fixnums, and if overflow happens it signals errors. (COMPLEX FIXNUM) does not exist because common lisp does not allow a complex with imagpart 0.
13:05:26
guicho
flip214: but you cannot make a specialized array for (COMPLEX BIT), SBCL does not have it
13:06:36
guicho
heisig: Still struggling to publish it. I have some backer in my company, and hoping it helps. arademaker and fsmunos
13:14:32
guicho
heisig: since I implemented the inference part, you can focus on the distributed part in PetaLisp with the limited type subset you currently have
13:16:34
guicho
heisig: the distributed computation part and the lazy compilation part are your skill set and are more important for your your research question.
13:22:38
heisig
guicho: One more remark - I had yet another idea for type inference over the last few days.
13:23:30
heisig
guicho: Instead of working with type specifiers, one could work with integers that store a bitvector representation of each type as in Baker's subtypep paper.
15:37:49
jsatk
Thanks for the kind replies and investigation sjl & p_l. (I'm actually using sjl's "A Road to Common Lisp" article to learn)
15:37:51
jsatk
My computer went to sleep and lost connection so I may have lost some chat history. Was their ever a resolution?
15:39:26
p_l
jsatk: yeah, just run it as normal - some warnings are expected, because some implementations are bit more strict about what they see as "code smells" and sometimes you get a warning on "hey, I couldn't figure how to optimize that part, sorry"
15:39:53
p_l
jsatk: I have personally used compiler warnings about unsuccessful optimization as guide when optimizing code :)
15:41:55
jsatk
$ sbcl --load ~/.vim/pack/minpac/start/vlime/lisp/start-vlime.lisp 👈 This is all I'm running and it produces the aforementioned errors.
15:42:46
selwyn
p_l: sometimes i get remarks from SBCL about the 'cost' of various operations. does this usually indicate that the 'code smells?' or is it not possible to conclude anything without investigating more
15:57:09
sjl_
jsatk: yeah this is just a usocket problem that is already fixed, but the fix unfortunately just missed the cutoff for the latest quicklisp dist
16:15:43
fivo
Does anybody know if there is a function in asdf that returns all the systems defined in a directory and its subdirecotries?
16:18:56
jsatk
I'm doing the Vlime tutorial and I'm like grinning ear to ear. It boggles my mind that this old-as-hell language has such a nice and mature way to work with it (that doesn't require an IDE). My day-to-day work is modern web stuff (React, Node, Python, etc). Why don't those have tools this mature? 😢
16:25:16
White_Flame
selwyn: those are just "notes", not warnings or anything. It's just telling you that there are still runtime checks & generic handler calls being made, in situations where it does have extra optimization steps that it can't there due to type uncertainty