libera/#commonlisp - IRC Chatlog
Search
19:31:32
Guest491241242
NotThatRPG: thanks, currently I don't have a need to use separate distributions or create my own. At some point I had tried something with ultralisp but had not remembered to change it back quicklisp's distribution.
19:53:14
NotThatRPG_away
stylewarning: ? You mean you want to add a new component type that's a conda package? a conda environment?
20:16:34
NotThatRPG_away
Shinmera: I just noticed -- your documentation is a mess! or ... a ".mess" ;-)
20:18:19
NotThatRPG
It occurs to me that it would be nice if we could create a new dist that is just pointers into other dists, without having to actually replicate, but I don't know how hard that would be. HTTP redirection?
20:20:06
Shinmera
or rather, each dist release includes an url for each project's release that it includes.
20:23:33
Shinmera
I also would like to support it using another dist as a project's source (with replication)
20:29:47
stylewarning
NotThatRPG: I'm not 100% sure. I'm thinking of something like :depends-on which ensures foreign dependencies are loaded (?) or installed (?)
20:34:19
Shinmera
stylewarning: I have thought about that problem before but I honestly think it's not a great idea because of the massive diversity of system configuration tools out there that would need to be handled, not to mention the massive variance in *versions* those tools provide.
20:34:41
Shinmera
Instead, if I write a bindings library, I instead ship a version for every platform with the sources.
20:35:29
Shinmera
Once Forge is in a more state of actual existance I want to switch to building the foreign libraries, though.
20:35:30
NotThatRPG
stylewarning: If you want to do that you need to tell ASDF what a conda dependency is. Thinking not very hard about this, I would suggest: (1) you would need to give ASDF some way to find (or create) a conda env that contains the python systems you want. Maybe make a mixin for class (to add to ASDF system classes) to allow an ASDF lisp system to be associated with a conda env. (2) add a SECOND subclass of ASDF system that
20:35:30
NotThatRPG
corresponds to a python package, call it PYTHON-SYSTEM. Then you would have to add (at least) a PERFORM LOAD-OP method for PYTHON-SYSTEM that would know how to load a python system into the conda environment.
20:36:53
NotThatRPG
It's not great that python has so many different loading methods. If your user doesn't have conda installed, and just uses pyenv, for example, they would be SoL.
1:19:48
atgreen
_death, hayley .. reverting SBCL from 2.2.7 to 2.2.6 solved my corruption error from earlier today
1:27:04
hayley
I'm too busy today to look through the cl-postgres code, but it is still possible that it is modifying literals in a way that isn't allowed in Common Lisp, and it's caught by SBCL 2.2.7 now.
1:29:04
hayley
...after a quick glance that doesn't seem likely, but there is a (optimise (safety 0)) declaration that you could remove.
1:46:36
hayley
(setf (aref "blab" 2) #\u) is undefined behaviour. After SAVE-LISP-AND-DIE, SBCL 2.2.7 would put that string in read-only memory, so trying to write to the string would cause a memory fault.
1:47:02
hayley
But I don't think that's the issue; the use of (safety 0) in that function causing a memory fault is more concerning to me now.
3:17:56
aeth
easy bonus points to score: submit PRs to remove all (safety 0) except when the (safety 0) actually has a purpose (basically, to remove bounds checks) and even then you can probably move it to a tightly bound LOCALLY (instead of the typical function scope) to limit the chance of bugs surfacing there