<fnstudio_>hey, i've tried to build a 500x500x500 array and all seems to be fine; if i try with a 1000**3 array though, that will fail - it says "killed" <fnstudio_>of course, i imagine i'm allocating too much mem <fnstudio_>i was curious to know where the "bottleneck" (or "safeguard mechanism") is <fnstudio_>e.g. built-in as a constraint in the Guile interpreter or rather at the OS level or something else? <tohoyn>daviid: gtk-css-provider-load-from-data doesn't work. do you want a snippet? ***nckx is now known as nckxmas
<tohoyn>daviid: I'll make the snippet later today <taylan>fnstudio_: if the guile process just abruptly ends with the message "killed" then I think that's the OS killing it <rlb>I'm trying to figure out what a guile dialect should do wrt autocompilation -- i.e. how does it know whether or not it should autocompile (assuming it's trying to respect guile's normal behavior there)? (Also not sure I fully understand what I'm doing there yet...) <rlb>Hey, seems like maybe your git server's having trouble (didn't know if you knew): <rlb>oops - wrong channel <rlb>...wrt compilation, right now what I do is just call compile-file with (compiled-file-name) once I determine that we need to (this is for indirectly "required" modules), but that's perhaps wrong if auto-compilation is disabled via the envt, cmdline, etc. <fnstudio_>i'll experiment with the stack overflow mechanism then, thanks <pinoaffe>daviid: thanks for the info! I'll try and see which one of em fits my needs best