<happy_gnu[m]>And how, if in a simulation, maybe things are empty until you open them <happy_gnu[m]>Of course I am not physicists neither a computer scientists <happy_gnu[m]>But Schrödinger's cat seems to me is like lazy evaluation it doesn't happen until you call it <wingo>later tell stis: (5) yes, there is a finalizer slot on structs <sneek>wingo, stis says: I published the questions earlier, check the irc logs etc <wingo>sneek: later tell stis: (5) yes, there is a finalizer slot on structs <wingo>sneek: later tell stis: (4) what is a stalled thread? <wingo>sneek: later tell stis: (3) you mean compile-time warnings? yes it would be nice in some ways if there were a warning handler as a fluid or soemthing <wingo>sneek: later tell stis: (2) you can always build such a procedure of course :) <wingo>sneek: later tell stis: (1) yeah really sorry about the guile maintenance situation! for me things will be better at end of october. but feel free to post and re-post until it gets attention :) <amz3>I successfuly installed guix in a debian stretch lxc <amz3>I don't know what happened but 'guix pull && guix package -u' worked ***dsmith is now known as dsmith-work
<civodul>amz3: why "i don't know what happened"? :-) <civodul>sounds like: "surprisingly, it actually worked" <amz3>civodul: a few days agao, I did the same commands and it failed with an error, I did not report <amz3`>so I have an 'assoc' validation "framework" <amz3`>basically a '(validate spec assoc)' where SPEC is itself a an association between symbols and procedures that must throw a validation-error if the passed value is not good <amz3`>validate first checks that spec and assoc have the same keys and the proceed to check every value of ASSOC with the associated procedure in SPEC <amz3`>that's all I did last night... <amz3`>(I have the feeling that I am coding more slowly nowdays, but it might be because I have to implement things that I never implemented before) <amz3`>anyway, I will post the code of that validation thing <amz3`>once I have a complete test suite <OrangeShark>amz3`: that sounds like something for input validation, is that what you plan to use it for? <amz3`>janneke: I know you are working on bootstraping, I hope some day I will grow wiser reading all your wor <janneke>amz3`: i "just" started and learned while doing :-) <amz3`>well, still you have the gut to do it <amz3`>most of the work I do, I know how to do it, I have to fight laziness <davexunit>dustyweb: do you know how GOOPS handles the "diamond problem"? <davexunit>that is, a class D that inherits from classes B and C, where classes B and C inherit from class A. <davexunit>dustyweb: nvm I found the "class precendence list" section in the manual <dustyweb>davexunit: yeah it can be just as screwed as any other multiple inheritance system :) <dustyweb>but you can introspect the precedence list ***do is now known as w1gz
***do is now known as w1gz