libera/#commonlisp - IRC Chatlog
Search
1:25:42
nyx_land
the real problem with guix IME as a Common Lisp person is that it doesn't feel at all like it's designed to be a fully interactive environment like CL. you write code, you recompile everything, you can't inspect the running system live really (there's Geiser but I found it to be a very subpar experience). on top of that, developing CL with guix tooling feels very unnatural.
1:26:19
nyx_land
an init system in CL would be really cool, not sure why no one has ever attempted something like that but it's probably way more complicated that I'm aware of
1:27:03
nyx_land
a CL package manager would be a slog just based off my experiences making packages for nix and guix
8:34:33
Guest69
Sorry to crosspost from #ecl if that is not good boy behaviour, but I'm having troubles doing basic stuff like getting function info via describe/inspect or requiring uiop; any kind soul to help a noob?
8:37:52
pjb
Guest69: uiop is part of asdf. You should install quicklisp anyways. Have a look at http://cliki.net/Getting+Started
8:38:49
pjb
No. Install quicklisp, it makes its own installation of asdf. Avoid cl- packages from linux distributions.
8:40:09
jackdaniel
a known issue. it does not fail, it is just that for some core functions the necessary information is not recorded
8:40:26
jackdaniel
essentially ecl holds metainformation about functions in a separate file accessed with interface provided by ecl-help module
8:41:08
jackdaniel
if you define a function in the repl, then the prototype will be available, but unless you save that data, when you load the fasl in the fresh image this information will be gone
9:22:55
hayley
Because they chose to write it like that. But only the text format is similar to Lisp, and it's different enough that trying to read it with a CL reader is not pleasant.
9:23:42
hayley
e.g. https://github.com/no-defun-allowed/wasm2ps/blob/master/Code/reader.lisp And I recall...memory instructions(?) have an annoying "align=X" syntax that I haven't touched, because wasm2ps doesn't handle memory instructions.
9:25:02
hayley
If I recall correctly, they could benefit from learning that we have #- instead of #_, and don't put our close-parens on their own lines (though I know Z3 also messes up the latter, as smt-lib is also S-expression based).
9:25:38
Nilby
assembly code is already in prefix, e.g. "oper arg arg ...", but is delimited by source lines. turning it into s-exps is trivial and makes so you can group it not by line.
9:26:43
rendar
i made a small language with prefix `oper arg arg` where you can specify some arg "out of band data" with [], e.g. `oper arg[opts] arg[opts2]`
9:49:59
hayley
It won't, because approximately no web developer touches the text serialisation of WebAssembly.
9:51:15
hayley
(Contrived counter-point: it contributes to the mystification of Lisp, because people will think it's something their favourite compiler spits out. As some have pointed to intermediate representations in GCC and said "Look, Lisp is in your C compiler!" for little reason, after seeing ().)
9:51:41
hayley
No source-level debugging? It would be like debugging a C program by starting at the generated assembly.
9:53:13
Nilby
well hopefully at the very least it will make life easier for us, when we can just cl:read wasm and use macros on it