IRC channel logs
2023-02-15.log
back to list of logs
<jlicht>Are there load order guarantees for "#:use-module" when using `define-module'? <flatwhatson>jlicht: they're imported in order if that's what you're asking <jlicht>(I know there currently is an order; I'm wondering whether I should feel free to depend on this order not changing) <flatwhatson>i think it's safe to assume later imports will override conflicting defs from earlier imports <flatwhatson>but if you're relying on load-time side effects in those modules, that's a bad idea <flatwhatson>better than having conflicting imports is to explicitly disambiguate with select/rename/prefix <jlicht>One particular import tweaks the load-path (in an intended way), so it's pretty relevant that the order I see is the order I get. <old>jlicht: I personnaly alway do my import alphabetically <old>Thus, not relying on any explicit order <flatwhatson>jlicht: for load-path, IMO it's generally better to do this in a top-level script <flatwhatson>that said, (gnu packages) from guix relies on load-time manipulation of %load-path <old>we've entered a new age <old>Guile is the new javascript <drakonis>to be fair, i was thinking more of how js started as scheme <old>next step is linux kernel in pre-scheme <Zelphir>Brendan Eich can rest in piece, knowing, that the wrongs inflicted upon the world, will be righted. <drakonis>the next step is making a kernel derived language with scheme <mwette> so guile will also move (at least some stuff) to WASI <Zelphir>I should have written: "Will be able to rest in piece" <dthompson>we will have a capabilities oriented microkernel in 2025 ;) <BitPuffin>I wanted to watch the fosdem pre-scheme talk but mime memes <BitPuffin>was especially excited since I was messing a bit with pre-scheme <dthompson>all the online talk videos had some sort of issue and they were all taken down. <dthompson>not sure what the issue was but several people watched part of the prescheme talk and it was fine as far as they could tell <BitPuffin>is it technical or some weird copyright crap <BitPuffin>yeah felt kinda bad linking the prescheme talk to a friend who was also excited about prescheme before I realized the video doesn't work <dthompson>there are several videos I'd like to watch once everything is uploaded. <dthompson>just my luck, some of the ones I watched live are available but none of the ones I missed are. :) <BitPuffin>yeah was pretty happy to stumble upon the archive since it wasn't on typical vid sites but then immediately sad when the videos didn't work <BitPuffin>wingo talk was available though so that was nice <dthompson>most of the online sessions were streamed too early for my timezone <drakonis>i'm just disappointed at how long its taking to get the online sessions up <dsmith-work>wingo: Just got done watching your talk. Do I understand correctly that the wasm work will eventually lead to Guile native executables? <wingo>dsmith-work: (tx :) humm it's hard to tell! in the sense that guile->wasm leads to guile running without libguile, maybe. there are similar whole-program-compilation concerns there. <ArneBab>wingo: great news! Congrats on the cool project! <lfam>ACTION another one to say "enjoyed your talk!" <jpoiret>i cannot wait for Guix to run in Electron <old>jpoiret: Let's not go that way please <old>I want to keep my sanity intact <jpoiret>imagine the possibilities: instead of a bitcoin miner, you add a hidden guix build agent on your website <old>Imagine actually enjoying doing web stuff <old>that would now be possible :D