jackdaniel changed the topic of #commonlisp to: Common Lisp, the #1=(programmable . #1#) programming language | Wiki: <https://www.cliki.net> | IRC Logs: <https://irclog.tymoon.eu/libera/%23commonlisp> | Cookbook: <https://lispcookbook.github.io/cl-cookbook> | Pastebin: <https://plaster.tymoon.eu/>
dnhester has joined #commonlisp
akoana has joined #commonlisp
dnhester has quit [Ping timeout: 252 seconds]
dnhester has joined #commonlisp
dnhester has quit [Ping timeout: 248 seconds]
random-nick has quit [Ping timeout: 252 seconds]
JuanDaugherty has quit [Quit: JuanDaugherty]
dnhester has joined #commonlisp
evasync has quit [Ping timeout: 245 seconds]
evasync has joined #commonlisp
dnhester has quit [Ping timeout: 258 seconds]
xlymian has quit [Remote host closed the connection]
akoana has quit [Ping timeout: 272 seconds]
istewart has joined #commonlisp
amb007 has joined #commonlisp
amb007 has quit [Ping timeout: 252 seconds]
jonatack has quit [Ping timeout: 248 seconds]
triffid has joined #commonlisp
lucasta has quit [Quit: Leaving]
awlygj has joined #commonlisp
edgar-rft has quit [Quit: don't waste your life by reading this]
dnhester has joined #commonlisp
Pixel_Outlaw has quit [Read error: Connection reset by peer]
dnhester has quit [Ping timeout: 248 seconds]
dnhester has joined #commonlisp
dnhester has quit [Ping timeout: 255 seconds]
Pixel_Outlaw has joined #commonlisp
Lord_of_Life has quit [Ping timeout: 272 seconds]
X-Scale has joined #commonlisp
Lord_of_Life_ has joined #commonlisp
Lord_of_Life_ is now known as Lord_of_Life
eddof13 has joined #commonlisp
eddof13 has quit [Client Quit]
xlymian has joined #commonlisp
awlygj has quit [Quit: leaving]
xlymian has quit [Ping timeout: 276 seconds]
xlymian has joined #commonlisp
xlymian has quit [Ping timeout: 276 seconds]
xlymian has joined #commonlisp
jonatack has joined #commonlisp
xlymian has quit [Ping timeout: 276 seconds]
xlymian has joined #commonlisp
istewart has quit [Quit: Konversation terminated!]
fe[nl]ix has quit [Quit: Valete!]
shawnw has quit [Ping timeout: 248 seconds]
Guest45 has quit [Quit: Client closed]
fe[nl]ix has joined #commonlisp
Oddity has quit [Ping timeout: 272 seconds]
decweb has quit [Ping timeout: 252 seconds]
amb007 has joined #commonlisp
amb007 has quit [Read error: Connection reset by peer]
amb007 has joined #commonlisp
awlygj has joined #commonlisp
Oddity has joined #commonlisp
xlymian has quit [Ping timeout: 276 seconds]
shawnw has joined #commonlisp
dnhester has joined #commonlisp
xlymian has joined #commonlisp
dnhester has quit [Ping timeout: 252 seconds]
markb1 has quit [Read error: Connection reset by peer]
xlymian has quit [Ping timeout: 276 seconds]
X-Scale has quit [Quit: Client closed]
xlymian has joined #commonlisp
evasync has quit [Ping timeout: 252 seconds]
markb1 has joined #commonlisp
evasync has joined #commonlisp
Pixel_Outlaw has quit [Quit: Leaving]
xlymian has quit [Ping timeout: 276 seconds]
xlymian has joined #commonlisp
evasync has quit [Ping timeout: 272 seconds]
xlymian has quit [Ping timeout: 276 seconds]
xlymian has joined #commonlisp
pve has joined #commonlisp
zxcvz has joined #commonlisp
younder has joined #commonlisp
younder has quit [Remote host closed the connection]
younder has joined #commonlisp
Oddity has quit [Ping timeout: 252 seconds]
edgar-rft has joined #commonlisp
bjorkint0sh has joined #commonlisp
dnhester has joined #commonlisp
delyan_ has quit [Ping timeout: 260 seconds]
bjorkintosh has quit [Ping timeout: 260 seconds]
|3b| has quit [Ping timeout: 260 seconds]
Irvise has quit [Ping timeout: 260 seconds]
drakonis has quit [Ping timeout: 260 seconds]
mal1 has quit [Ping timeout: 260 seconds]
|3b|` has joined #commonlisp
xlymian has quit [Ping timeout: 276 seconds]
Irvise has joined #commonlisp
delyan_ has joined #commonlisp
danse-nr3 has joined #commonlisp
drakonis has joined #commonlisp
mal1 has joined #commonlisp
dnhester has quit [Ping timeout: 252 seconds]
herjazz has joined #commonlisp
shka has joined #commonlisp
xlymian has joined #commonlisp
zxcvz has quit [Quit: zxcvz]
King_julian has joined #commonlisp
dnhester has joined #commonlisp
xlymian has quit [Ping timeout: 276 seconds]
evasync has joined #commonlisp
dnhester has quit [Ping timeout: 248 seconds]
evasync has quit [Changing host]
evasync has joined #commonlisp
xlymian has joined #commonlisp
dino_tutter has joined #commonlisp
xlymian has quit [Ping timeout: 276 seconds]
xlymian has joined #commonlisp
dnhester has joined #commonlisp
danse-nr3 has quit [Quit: on the move]
danse-nr3 has joined #commonlisp
|3b|` is now known as |3b|
kamafam has joined #commonlisp
mandw has quit [Remote host closed the connection]
mandw has joined #commonlisp
akoana has joined #commonlisp
danse-nr3 has quit [Ping timeout: 248 seconds]
jrx has joined #commonlisp
xlymian has quit [Remote host closed the connection]
dnhester has quit [Ping timeout: 264 seconds]
waleee has joined #commonlisp
akoana has quit [Ping timeout: 248 seconds]
X-Scale has joined #commonlisp
danse-nr3 has joined #commonlisp
xlymian has joined #commonlisp
dnhester has joined #commonlisp
X-Scale has quit [Quit: Client closed]
mgl_ has joined #commonlisp
mgl has joined #commonlisp
mgl_ has quit [Ping timeout: 252 seconds]
JuanDaugherty has joined #commonlisp
danse-nr3 has quit [Ping timeout: 255 seconds]
mgl has quit [Ping timeout: 252 seconds]
liminality has joined #commonlisp
<liminality> hi all
<liminality> where can i learn more about reducing how many bytes are consed by my code?
mgl has joined #commonlisp
jonatack has quit [Ping timeout: 252 seconds]
alcor has joined #commonlisp
alcor has quit [Remote host closed the connection]
<Shinmera> don't know about learning, but profilers like sb-aprof and sb-sprof can tell you where you cons, if your code is vast. otherwise, uh, don't use functions that allocate?
<pranav> liminality: Some algorithms and data structures book?
<pranav> Use Inplace algorithms...
<liminality> Shinmera! hi! :) I love your precise-time library. what does allocating look like?
random-nick has joined #commonlisp
<Shinmera> (list ..) (copy-seq ..) (make-instance ...) (cons ..) etc
<liminality> @pranav Inplace algorithms? Also, would um... "Introduction To Algorithms" be a good book for that? I've had it sitting around for ages but didn't know if it was worth the read.
<liminality> @Shinmera oh... okay yeah I use a lot of those.Thanks :)
<Shinmera> there's no exhaustive list of functions that allocate, but in general it's anything that returns a "fresh object"
<Shinmera> though allocation can also happen if you use bignums, complex numbers, and ratios
<pranav> liminality: Inplace algorithms usually only use a fixed/constant amount of memory other than the input. They modify the input data structures.
<Shinmera> or double floats
<liminality> that makes sense... things that work on and return copies of the given objects, instead of working destructively in-place?
<Shinmera> right
<liminality> pranav: oh i see it's a whole like, field of study. this really helps, thank you =)
<pranav> Does anyone use cons pools these days?
<liminality> (idk what a cons pool is)
<pranav> The kind described in Let over Lambda, iirc.
<Shinmera> pranav: I use pools, though not for conses
<Shinmera> heavier things whose lifetime is well defined
<Shinmera> though SBCL's stack allocation has gotten pretty good lately (thanks Charles) so even that I use less and less
<liminality> Shinmera: i know it's a bit off-topic and you must get this a lot, but i really really really appreciate everything you've done for the CL ecosystem. every time i introduce CL to someone, i direct them to portacle, and when they start asking about making games in lisp, i point them to Kandria. you're a huge inspiration.
<Shinmera> I don't get it that much, but thank you
<Shinmera> Wish I had the energy to keep portacle updated
<liminality> the last win10 binary w/ SBCL 2.0.0. is still fairly new, and if ever its an issue then people can just build portacle from one of your releases or even just change the version-number themselves :) honestly i've never had anyone complain about it
<Shinmera> well, windows isn't the problem child
<liminality> oh? is it linux or mac that's giving issues?
<Shinmera> mac, of course
<Shinmera> and linux because deploying anything on linux is hard
<liminality> naruhodo
JuanDaugherty has quit [Quit: JuanDaugherty]
<Shinmera> anyway, I just don't have the time I used to anymore, and maintaining portacle specifically is arduous enough that in all the years since I stopped maintaining it nobody else has felt like taking up the reigns either
<Shinmera> makes me wonder if I should maybe think about a contingency for all the other libraries of mine
waleee has quit [Ping timeout: 260 seconds]
mgl has quit [Remote host closed the connection]
xlymian has quit [Remote host closed the connection]
<liminality> a contingency?
xlymian has joined #commonlisp
<Shinmera> some way for someone else to gain access
<pranav> liminality: Insurance.
<liminality> hmmmm...... i mean, aren't all your projects' repos public?
<Shinmera> they sure are
<Shinmera> but things reference those repos and if someone forks nobody knows about it
<liminality> ahh.... so you want to be able to give someone direct control over the original repos, in the event you can't access/update them anymore?
<Shinmera> yes
<liminality> deadman switch >:3c
donleo has joined #commonlisp
dnhester has quit [Ping timeout: 252 seconds]
mwnaylor has quit [Ping timeout: 252 seconds]
<liminality> Shinmera: hey i know its annoying to bring it up again but one of my friends just wanted to relay a message; "Can you tell Shinmera I love Portacle from the bottom of my heart. So many headaches skipped."
<Shinmera> haha, thank you
<beach> liminality: Why is it important to you how much memory is allocated?
X-Scale has joined #commonlisp
<liminality> beach: hey, long time no see :) i'm creating 3D meshes at runtime, but the heap gets exhausted when i try to make too many of them with lots of verts. i've allocated 8GB to SBCL, though even that's already too big for my tastes. there aren't any memory leaks. i want the project to run on much smaller amounts of RAM, something like 2GB.
<liminality> pranav pointed me to inplace algos and Shinmera told me about some funcs that allocate, so that'll help
<Shinmera> sb-sprof is my goto to figure out where stuff is happening
<beach> liminality: It sounds like you need to come up with a more compact representation of your meshes.
varjag has joined #commonlisp
<beach> In-place algorithms won't help if the memory that is ultimately referenced is already too big.
<liminality> mmmmaybe yeah. honestly it's a Minecraft clone, so the meshes are chunks, each made of cubes. I was thinking of maybe writing a geometry shader that emits a cube, but that'd be running up to like hundreds of times per chunk, per frame, and making the data once and uploading it to the gpu in a buffer just means much less redoing-of-work.
<liminality> or i guess i could just make more chunks and have them each be smaller? hmm...
<Shinmera> you'll want an array representation for the blocks and a marching cubes algorithm to generate a mesh of the surface described by the voxelised representation
X-Scale has quit [Ping timeout: 256 seconds]
<liminality> do you recommend putting the marching-cubes algo in a shader and uploading a buffer holding the voxelised representation, or rather to compute the mesh w/ marching cubes on cpu then upload the result?
<Shinmera> you can't do marching cubes in a shader
<liminality> aw
<Shinmera> and even if you could it would be wasteful
<Shinmera> the mesh of a chunk is mostly fixed, so it should be computed once when it changes and cached to a buffer
<liminality> gotcha.
dnhester has joined #commonlisp
brokkoli_origin has quit [Ping timeout: 252 seconds]
prokhor has joined #commonlisp
brokkoli_origin has joined #commonlisp
dnhester has quit [Ping timeout: 252 seconds]
m5zs7k has quit [Ping timeout: 244 seconds]
Din has joined #commonlisp
Din has quit [Client Quit]
m5zs7k has joined #commonlisp
dnhester has joined #commonlisp
Demosthe1ex is now known as Demosthenex
ym has joined #commonlisp
dnhester has quit [Ping timeout: 252 seconds]
xlymian has quit [Ping timeout: 276 seconds]
alcor has joined #commonlisp
dnhester has joined #commonlisp
King_julian has quit [Ping timeout: 258 seconds]
dnhester has quit [Ping timeout: 264 seconds]
xlymian has joined #commonlisp
xlymian has quit [Remote host closed the connection]
xlymian has joined #commonlisp
prokhor has quit [Ping timeout: 252 seconds]
prokhor has joined #commonlisp
jrx has quit [Quit: ERC 5.5.0.29.1 (IRC client for GNU Emacs 29.4)]
dnhester has joined #commonlisp
evasync has quit [Ping timeout: 264 seconds]
decweb has joined #commonlisp
danse-nr3 has joined #commonlisp
evasync has joined #commonlisp
pkal has joined #commonlisp
waleee has joined #commonlisp
kamafam has quit [Read error: Connection reset by peer]
King_julian has joined #commonlisp
danse-nr3 has quit [Quit: lunch]
uhuh has joined #commonlisp
Oddity has joined #commonlisp
evasync has quit [Ping timeout: 258 seconds]
<dnhester> Shinmera: thanks for the reply!
herjazz has quit [Quit: leaving]
X-Scale has joined #commonlisp
evasync has joined #commonlisp
evasync has quit [Changing host]
evasync has joined #commonlisp
<beach> What is the purpose of the ENVIRONMENT optional parameter to UPGRADED-ARRAY-ELEMENT-TYPE?
X-Scale has quit [Ping timeout: 256 seconds]
contrapunctus has quit [Ping timeout: 252 seconds]
danse-nr3 has joined #commonlisp
contrapunctus has joined #commonlisp
<beach> If an implementation has specialized array types for (UNSIGNED-BYTE <mumble>) and (SIGNED-BYTE <mumble>), which one is the most specialized? That is, if a type specifier is a subtype of both those two, which one should be the result of UPGRADED-ARRAY-ELEMENT-TYPE?
<scymtym> beach: probably so that something like (typexpand type-specifier environment) can be applied if the supplied type specifier is not one of the built-in ones
<beach> scymtym: That makes a lot of sense. Thank you.
<bike> beach: sbcl has a bunch of upgraded array element types like (unsigned-byte 7) to make this unambiguous (or at least i think that's why)
<beach> bike: I see. That also makes sense, kind of.
<bike> of course this is also why sbcl has nil arrays
<beach> I kind of remember that, but I can't remember why. It will take me a while to refresh my memory.
<beach> scymtym: So I guess I just have to pass on the ENVIRONMENT argument to SUBTYPEP.
<bike> NIL is a subtype of both BASE-CHAR and BIT. therefore the UAET of nil must be a subtype of the UAET of base-char and of the UAET of bit. they are their own UAETs, so the UAET of NIL must be a subtype of both BASE-CHAR and BIT. but the only such type is NIL.
<beach> Heh, makes sense.
danse-nr3 has quit [Quit: power]
xlymian has quit [Ping timeout: 276 seconds]
Perflosopher1 has joined #commonlisp
Perflosopher has quit [Ping timeout: 248 seconds]
Perflosopher1 is now known as Perflosopher
danse-nr3 has joined #commonlisp
<beach> Oh, great! So MAKE-ARRAY doesn't have an ENVIRONMENT parameter.
<beach> I guess one has to be added.
jrm has quit [Read error: Connection reset by peer]
<bike> adjust-array, as well
jrm has joined #commonlisp
<beach> Indeed.
xlymian has joined #commonlisp
xlymian has quit [Ping timeout: 276 seconds]
xlymian has joined #commonlisp
uhuh has quit [Remote host closed the connection]
uhuh has joined #commonlisp
xlymian has quit [Ping timeout: 276 seconds]
xlymian has joined #commonlisp
<paulapatience> liminality: If you need marching cubes, I can polish up my implementation (in CL) and release it. It's based on a paper from 2016 and fixes many ambiguity errors in the previous "best" algorithm from 2003.
<paulapatience> It's able to generate 500 MiB meshes with 16 GiB of memory in 2 minutes. Don't know if that would be good for you or not.
<liminality> paul: hey, thanks :) i'm making blocky terrain so i'm not sure if marching cubes would be what i need, and rolling my own mesher from the ground up would just mean a lot more precise control on my end over what i need. but it sounds really cool
<liminality> ah... 500MiB... das a lot of verts, god damn
<liminality> are you using floats to describe the vert positions or?
kamafam has joined #commonlisp
<paulapatience> A ub32 vector of indices pointing into a float vector of vertices
<paulapatience> I think it was like 12 million vertices, 6 million triangles or something along those lines
waleee has quit [Ping timeout: 248 seconds]
<paulapatience> Anyway, if ever you want to try it out, let me know. I've been intending to release it but have had some other things going on. I didn't find a better algorithm of marching cubes in my research. There may be faster ones, maybe using parallelism, but they don't deal with all the ambiguities. So it depends on what your needs are.
JuanDaugherty has joined #commonlisp
<Shinmera> there's not really any ambiguities when it comes to voxelised cube marching at least
<Shinmera> either way the base algorithm remains, just the voxel selection is simpler
<paulapatience> Good point
donleo has quit [Remote host closed the connection]
donleo has joined #commonlisp
cage has joined #commonlisp
cage has quit [Excess Flood]
xlymian has quit [Read error: Connection reset by peer]
cage has joined #commonlisp
shawnw has quit [Ping timeout: 252 seconds]
danse-221 has joined #commonlisp
jonatack has joined #commonlisp
danse-nr3 has quit [Ping timeout: 248 seconds]
uhuh has quit [Ping timeout: 252 seconds]
dnhester has quit [Ping timeout: 260 seconds]
molson has joined #commonlisp
molson_ has quit [Ping timeout: 252 seconds]
King_julian has quit [Ping timeout: 252 seconds]
X-Scale has joined #commonlisp
waleee has joined #commonlisp
molson has quit [Remote host closed the connection]
molson has joined #commonlisp
dnhester has joined #commonlisp
waleee has quit [Ping timeout: 260 seconds]
X-Scale has quit [Ping timeout: 256 seconds]
varjag has quit [Quit: ERC (IRC client for Emacs 27.1)]
molson has quit [Remote host closed the connection]
JuanDaugherty has quit [Quit: JuanDaugherty]
molson has joined #commonlisp
kamafam has quit [Read error: Connection reset by peer]
uhuh has joined #commonlisp
molson has quit [Remote host closed the connection]
molson has joined #commonlisp
kamafam has joined #commonlisp
molson has quit [Remote host closed the connection]
lucasta has joined #commonlisp
molson has joined #commonlisp
yitzi has joined #commonlisp
eddof13 has joined #commonlisp
dnhester has quit [Ping timeout: 252 seconds]
cage has quit [Read error: Connection reset by peer]
cage has joined #commonlisp
cage has quit [Excess Flood]
cage has joined #commonlisp
liminality has quit [Ping timeout: 260 seconds]
dino_tutter has quit [Ping timeout: 252 seconds]
awlygj has quit [Quit: leaving]
markb1 has quit [Read error: Connection reset by peer]
alcor has quit [Remote host closed the connection]
alcor has joined #commonlisp
liminality has joined #commonlisp
NotThatRPG has quit [Ping timeout: 252 seconds]
dnhester has joined #commonlisp
markb1 has joined #commonlisp
dnhester has quit [Ping timeout: 260 seconds]
limiduality has joined #commonlisp
liminality has quit [Ping timeout: 252 seconds]
dnhester has joined #commonlisp
dnhester has quit [Ping timeout: 252 seconds]
evasync has quit [Ping timeout: 248 seconds]
danse-221 has quit [Quit: nice evening]
uhuh` has joined #commonlisp
shawnw has joined #commonlisp
uhuh has quit [Ping timeout: 264 seconds]
dnhester has joined #commonlisp
lucasta has quit [Quit: Leaving]
evasync has joined #commonlisp
dnhester has quit [Ping timeout: 248 seconds]
evasync has quit [Ping timeout: 260 seconds]
uhuh` has quit [Quit: ERC 5.5.0.29.1 (IRC client for GNU Emacs 29.1)]
NotThatRPG has joined #commonlisp
danse-nr3 has joined #commonlisp
amb007 has quit [Read error: Connection reset by peer]
amb007 has joined #commonlisp
waleee has joined #commonlisp
wacki has joined #commonlisp
evasync has joined #commonlisp
evasync has quit [Ping timeout: 248 seconds]
dnhester has joined #commonlisp
evasync has joined #commonlisp
dnhester has quit [Ping timeout: 252 seconds]
evasync has quit [Ping timeout: 252 seconds]
dino_tutter has joined #commonlisp
evasync has joined #commonlisp
evasync has quit [Ping timeout: 258 seconds]
shawnw has quit [Ping timeout: 248 seconds]
Pixel_Outlaw has joined #commonlisp
danse-nr3 has quit []
evasync has joined #commonlisp
evasync has quit [Ping timeout: 244 seconds]
dnhester has joined #commonlisp
evasync has joined #commonlisp
troojg has joined #commonlisp
evasync has quit [Ping timeout: 272 seconds]
troojg has quit [Ping timeout: 248 seconds]
evasync has joined #commonlisp
wobbol has quit [Ping timeout: 245 seconds]
user2 has joined #commonlisp
rtypo has joined #commonlisp
user2 has quit [Ping timeout: 252 seconds]
varjag has joined #commonlisp
hexa6 has quit [Ping timeout: 272 seconds]
user2 has joined #commonlisp
eddof13 has quit [Quit: eddof13]
cage has quit [Quit: rcirc on GNU Emacs 29.4]
dnhester has quit [Ping timeout: 260 seconds]
ym has quit [Ping timeout: 258 seconds]
user2 is now known as wobbol
King_julian has joined #commonlisp
amb007 has quit [Read error: Connection reset by peer]
mgl has joined #commonlisp
amb007 has joined #commonlisp
mrcom_ has joined #commonlisp
evasync has quit [Ping timeout: 248 seconds]
<aeth> limiduality: The easiest way to see where the surprise conses are in SBCL is to disassemble the function because SBCL helpfully comments the consing in its disassembly so you don't even have to read the assembly, you just can read the comments. Assuming the functions are short enough that that's all you need to narrow things down.
mgl has quit [Remote host closed the connection]
<limiduality> aeth: things like thread.alloc-region and ALLOC-TRAMP-R11?
mgl has joined #commonlisp
<aeth> yes
<aeth> Functions that don't cons (which should be most of them!) won't have that, which narrows down where your issues are.
<limiduality> paulapatience: i'd love to see the paper
<limiduality> aeth: thanks a ton :)
mwnaylor has joined #commonlisp
<selpoke> is consing bad
<aeth> selpoke: when you run out of heap space, yes
yitzi has quit [Ping timeout: 260 seconds]
ym has joined #commonlisp
yitzi has joined #commonlisp
<paulapatience> limiduality: The algorithm I ported is from https://github.com/rogrosso/tmc. The papers are linked at the bottom of the readme.
<ixelp> GitHub - rogrosso/tmc
<aeth> You have to (?) cons, you just want to have it done mostly up front, generally in arrays specialized to a specific numeric type (such as single-float) and not lists (should be 1/4 the space for large single-float data structures on 64-bit, and you get tightly packed and unboxed even if double-float)
<aeth> And what can't be done up front should probably be declared dynamic-extent (not heap allocated) for these sorts of algorithms
<limiduality> how would you declare a symbol as dynamic-extent? (declare (type dynamic-extent my-cool-symbol))?
<limiduality> paulapatience: tyvm :)
<aeth> not type, just dynamic-extent, but you should be careful that they're actually dynamic-extent (such as only used within a function) and don't need to be heap allocated
<aeth> Oh, and when using double-floats you have to be careful about all of the expression stuff that implicitly returns values even when it's used for the side effects (such as SETF) because double-floats can be optimized by the implementation to not use heap boxing (for the type tag!) if they don't escape function scope. They can still be read from or set into double-float arrays without heap boxing them.
<aeth> That is where surprise allocations usually happen.
<limiduality> huh..... interesting!
<aeth> Also, if lots and lots of allocations are an issue for you and you're using double-floats, then pure non-inline functions that return double-floats aren't a good idea. Single-floats shouldn't have this issue except in 32-bit (rather than 64-bit) implementations. This is because in dynamic typing, you need to also fit the type tag on the heap, not just the thing itself.
mgl has quit [Remote host closed the connection]
mgl has joined #commonlisp
<aeth> But I wouldn't be surprised if a GC can handle this sort of thing well.
eddof13 has joined #commonlisp
eddof13 has quit [Client Quit]
<NotThatRPG> Am I right in thinking that 5AM doesn't have a way to share fixtures between tests (i.e., the value of any binding in a fixture is NECESSARILY re-computed every time it's used)?
<bike> i believe that's correct? but of course you can have multiple checks in any given test
mgl has quit [Ping timeout: 258 seconds]
ym has quit [Ping timeout: 244 seconds]
evasync has joined #commonlisp
mgl has joined #commonlisp
evasync has quit [Ping timeout: 244 seconds]
yitzi has quit [Remote host closed the connection]
mgl has quit []
mgl has joined #commonlisp
chrcav has quit [Ping timeout: 252 seconds]
chrcav has joined #commonlisp
xlymian has joined #commonlisp
mgl has quit [Ping timeout: 248 seconds]
<NotThatRPG> bike: Yes, that's right, but if a check fails, because it's nameless, that can be a nuisance.
<NotThatRPG> I will add that to the set of features I will try to (find time to) add.
NotThatRPG is now known as NotThatRPG_away
NotThatRPG_away has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
NotThatRPG has joined #commonlisp
wacki has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
NotThatRPG has quit [Ping timeout: 252 seconds]
kamafam has quit [Ping timeout: 248 seconds]
evasync has joined #commonlisp
xlymian has quit [Remote host closed the connection]
chiselfuse has quit [Remote host closed the connection]
chiselfuse has joined #commonlisp
evasync has quit [Ping timeout: 260 seconds]
King_julian has quit [Ping timeout: 252 seconds]
X-Scale has joined #commonlisp
evasync has joined #commonlisp
alcor has quit [Remote host closed the connection]
evasync has quit [Ping timeout: 258 seconds]
X-Scale has quit [Ping timeout: 256 seconds]
<mwnaylor> What's advise for wanting code in a package that has not been made public via an export form? Stump WM has useful functions that would help with writing extentions, but I'm reluctant to use something that could change w/o notice, leading to my code breaking in the future.
akoana has joined #commonlisp
<mwnaylor> s/advise/advice/
evasync has joined #commonlisp
evasync has quit [Ping timeout: 244 seconds]
dino_tutter has quit [Ping timeout: 244 seconds]
evasync has joined #commonlisp
evasync has quit [Ping timeout: 272 seconds]
char has joined #commonlisp
pve has quit [Quit: leaving]
<jasom> mwnaylor: ask the author(s) their opinion on the stability of the symbols and the appropriateness of exporting them?
amb007 has quit [Ping timeout: 248 seconds]
akoana has quit [Quit: leaving]
evasync has joined #commonlisp
evasync has quit [Ping timeout: 252 seconds]
<mwnaylor> jasom: That's a good long term approach. Still leaves me in a quandry as to what I should do in the short term.
char has quit [Remote host closed the connection]
limiduality has quit [Ping timeout: 252 seconds]
varjag has quit [Ping timeout: 260 seconds]
yitzi has joined #commonlisp
evasync has joined #commonlisp
troojg has joined #commonlisp
donleo has quit [Ping timeout: 252 seconds]
evasync has quit [Ping timeout: 260 seconds]
amb007 has joined #commonlisp
random-nick has quit [Ping timeout: 260 seconds]
jonatack has quit [Ping timeout: 252 seconds]
amb007 has quit [Ping timeout: 264 seconds]
jonatack has joined #commonlisp
evasync has joined #commonlisp