<davexunit>could someone please explain the `pk` procedure? <nalaginrut>sneek: later tell davexunit pk is the alias of peek, and if you have nala-repl, you may use ,src to checkout its code, it's very easy <sneek>Welcome back Chaos`Eternal, you have 1 message. <dsmith>sneek, later tell davexunit For pk, look at the source in modules/ice-9/boot-9.scm There is a comment that describes useage ***Gues_____ is now known as Guest97227
<shanecelis>davexunit: Re: yesterday's convo. Maybe fluids are a good way to have customizable variables? <taylanub>Aren't fluids just the primitive feature backing parameters ? <davexunit>I feel like there's a simple answer to this. <sneek>Welcome back davexunit, you have 2 messages. <sneek>davexunit, nalaginrut says: pk is the alias of peek, and if you have nala-repl, you may use ,src to checkout its code, it's very easy <sneek>davexunit, dsmith says: For pk, look at the source in modules/ice-9/boot-9.scm There is a comment that describes useage <davexunit>but what does peek actually do? It seems to just output a commented sexp <taylanub>Just wrap an expression in (pk <expr>) and you'll have its value printed out during your test-run. <taylanub>It also returns <expr> itself so doesn't change the code's semantic.s ***bitdiddl` is now known as bitdiddle
***sneek_ is now known as sneek
***Gues_____ is now known as Guest25944