***sneek_ is now known as sneek
<nly>janneke: i redid mru from scratch. It's pushed to 'new-mru' branch. I hope the API has not changed. <nly>how can i use #:optional or similar thing for define-method in (oop goops) <wingo>sneek: later tell civodul tx! regarding #1, there is -Ono-letrectify <wingo>sneek: later tell civodul regarding #2, good question! i think letrectification should be on for -O2 at least and maybe -O1. currently it is on at -O1 <wingo>sneek: later tell civodul the only breakage can come from people mutating modules' internal bindings from outside the compilation unit. i am thinking that is rare enough that letrectification can be on by default, but dunno <janneke>nly: sadly, goops does not have #:optional or #:key yet, you must use a plain function or manually write all define-method's with different signatures <wingo>davexunit: i have a trig unboxing patch :) <lloda>got this error building last master on osx ERROR: asyncs.test: preemption via sigprof - arguments: ((wrong-type-arg #f "Wrong type (expecting ~A): ~S" ("resumable continuation" #<vm-continuation 1032755e0>) (#<vm-continuation 1032755e0>))) <lloda>it was a fluke, got through on retry <lloda>it's weird that error substs are printed that way <lloda>fairly sure that's not how it's supposed to be <lloda>or it's just not the normal report channel <lispmacs>hi, I was just wondering: how does an SCM object know whether or not some C data structure has a reference to it? Or does it? I was storing references to SCM objects in g_hash_tables and am wondering about this ***jao is now known as Guest61468
<civodul>i guess you perfectly answered my concerns :-) <civodul>there have been cases in the past where we monkey-patched internal bindings <civodul>this will no longer be possible, but that's probably an acceptable tradeoff <lispmacs>hi, I was just wondering: how does an SCM object know whether or not some C data structure has a reference to it? Or does it? I was storing references to SCM objects in g_hash_tables and am wondering about this