@shegeley@rml@cwebber most schemers are republicans, in the anti-monarchist sense :) but if the intended use case is global monkeypatching, then in guile `set!` is your tool. if `a` is exported, then just `set!` on `a`. if not, `(set! (@@ (X) a) new-val)`
@robinheghan only superficial, the kind you get after anything that requires stitches. nothing deep. a bit of an annoying place to have stitches, of course ;)
anyway this thread is for cishet men because i am sure trans/etc people are already aware of all the biology here. it is not right that women should have to be responsible for contraception and more men should consider the scissors! ✂️✂️✂️✂️
so my surgery is in a week. apparently is just outpatient surgery under sedation (not general anaesthesia). some countries normalize the idea that it is reversible but france’s official line is that it is definitive, apparently; reversal operations are like only 50% successful apparently?
here in france it takes a couple months at least to get the first appt with the urologist. (i did not know that urologists were the ones to do this. my grandfather was a urologist and i thought he just did urinary tract infections? apparently they do many things? i am a grown adult and yet v ignorant)
3. more ephemerally, i have a little bare-bones baseline-style compile-to-c scheme in the works. uses the c control stack but a side value stack, so as to have packed GC roots. the compiler is in scheme of course. the intent is to be a useful-enough approximation of a production system to use when testing https://github.com/wingo/whippet-gc/. who knows if it is fit for purpose though; will publish when it works 🤪
2. the work in that bobkonf talk for @spritelyinst is continuing apace; i think we are maybe 90% done for core Guile, e.g. call-with-prompt is working though abort-to-prompt isn't yet. still quite some prelude / stdlib work to do, and compiling multiple modules in a single compilation unit; maybe 2 calendar months out. Follow along at https://gitlab.com/spritely/guile-hoot if that is your thing.
very annoying: to properly benchmark a garbage collector with respect to a program, you need a production-quality compiler / language implementation. otherwise you don't know how much gc overhead (e.g. ensuring stack roots are precisely enumerable) is imposed by the compiler
by now it's clear that adaptive optimization is a universal technique that can make *any* program fast; enough speculative inlining at run-time (and dollars thrown at VM engineers) will burn away all abstractions. but there is more AOT compilation of dynamic languages than there used to be: Swift, Dart, JS via Hermes et al; and for AOT there is no one universal technique
@22 the stakeholders are j2wasm, the wasm-targetting successor of j2cl, a toolchain used for google sheets (not a secret); and https://kotlinlang.org/docs/wasm-overview.html. j2wasm isn't quite java, i think they are willing to accept some deviations. but yes people do want proper java on wasm/gc