IRC channel logs

<vagrantc>finally building rust-1.93.0 on aarch64-linux ... this is days in the making! :)

<ieure>"but it's the pelvic rust"

<ieure>that really drives you insay-ay-ay-ay-ayne

<vagrantc>really, really need to explore the newer versions of mrustc ... i don't even know rust, but this might drive me to just that sort of madness

<KJY> hey there, just kind of curious about the seemingly new (@ (gnu packages something) something) for packages. Haven't seen this system nor the message until I just did a pull and reconfigure. I assume this just removes the need for declaring the use-modules? Or is something else? Thanks!

<robin>KJY, i may be missing some context, but, @ is standard guile syntax for (@ <module-name> <variable-name>) to refer to a public variable from <module-name>, which can be used as an alternative to importing

<robin>(can also be used as the first arg to set! and in some other contexts, though, not a symbol so not a drop-in substitute for the name, in let-bindings for instance)

<KJY>Oh? In all of the docs I have seen and read it has me doing (use-modules (gnu packages wm)) at the top as an example, and in my home configuration I do (packages (list sway)) as a basic example and its telling me to use a new way of doing it so thats why I was confused; "warning: 'sway' is deprecated, use '(@ (gnu packages window-management) sway)' instead". I am pretty new to Scheme and Guix overall (only been using it a few months).

<KJY>seems like that method would lead to a lot more verbose code though unless you could do (@ (gnu packages window-management) (list sway swayidle swaylock)) or something akin to that?

<jresich>KJY I think that warning message is just a wierd edge case, what it's trying to say is that some package is deprecated and to use another; you don't have to use the @ syntax

<jresich>the @ syntax is just the most effective way to be specific about a scheme variable in that context

<KJY>Haha that would have made sense if I paid attention. I guess the syntax made me thing the whole thing had changed but looking at the log it is just in reference to packages under wm switching to be under window-management now. Thanks :)

<vagrantc>wellll... built all the intermediate rust versions from 1.55 up to 1.93 in two days. Now go is building.... :)

<vagrantc>or was it three days? hard to remember

<stikonas>in principle mrustc can bootstrap 1.91

<vagrantc>yes ... and given my last 2-3 days of compiling rust versions ... would be nice to leverage a newer mrustc that cuts the bootstrap path by ideally some 40 versions or so :)

<vagrantc>40 rust versions...

<vagrantc>looks like efraim is the last one to update the rust bootstrap with mrustc ...

IRC channel logs

2026-07-25.log