🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm
Set by lizmat on 8 June 2022.
01:22 vrurg joined, vrurg_ left 04:17 guifa left 04:56 Guest42 joined 04:57 Guest42 left 05:42 guifa joined 07:38 guifa left 11:42 librasteve_ joined
Geth rakudo/lizmat-rakudo-opt: 5db6992bd6 | (Elizabeth Mattijsen)++ | src/main.nqp
Be more specific about what is allowed in RAKUDO_OPT

Allowed are:
   -I -M --optimize --rakudo-home --debug-port --repl-mode
   --profile --profile-compile --profile-kind --profile-stage
   --stagestats --ll-exception --full-cleanup --debug-suspend
Added parameter --disable-rakudo-opt: if specified, then anything in RAKUDO_OPT will be ignored
14:46
[Coke] releasable6: next 16:50
releasable6 [Coke], Release date for Rakudo 2025.12 is listed in “Planned future releases”, but it was already released.
[Coke], and I oop! Backtrace: gist.github.com/b80444978a4a56ba4d...d2bddb2f2c
Geth rakudo/main: ce03d17010 | (Will Coleda)++ | docs/release_guide.pod
note next release date
16:53
[Coke] releasable6: next 16:56
releasable6 [Coke], Release date for Rakudo 2025.12 is listed in “Planned future releases”, but it was already released.
[Coke], and I oop! Backtrace: gist.github.com/86a6d7c124002fd6e4...6e41ce0497
16:56 guifa joined 17:34 guifa left
Geth rakudo/lizmat-rakudo-opt: 2aebaabf4c | (Elizabeth Mattijsen)++ | src/core.c/CompUnit/PrecompilationRepository.rakumod
Make sure RAKUDO_OPT doesn't get repeated when precomping

Any options of --ll-exception, --profile, --optimize and --target are passed to the process doing precompilation. If any of these was specified in the RAKUDO_OPT, they would be passed a second time (and a third when recursing, etc, etc).
... (7 more lines)
17:35
[Coke] releasable6: next 18:48
releasable6 [Coke], Next release in ≈19 days and ≈0 hours. There are no known blockers. 0 out of 8 commits logged
[Coke], Details: gist.github.com/9dbefd4189596a0af8...4ca983d350
[Coke] releasable6: next 18:55
releasable6 [Coke], Next release in ≈19 days and ≈0 hours. There are no known blockers. 8 out of 8 commits logged
librasteve_ rakudoweekly.blog/2025/12/29/2025-...the-onion/ 19:15
lizmat librasteve_++ 19:16
Geth rakudo/lizmat-rakudo-opt: f898b544e0 | (Elizabeth Mattijsen)++ | src/main.nqp
Handle "\ " as a sort of non-breaking space in RAKUDO_OPT

This should allow things like:
   RAKUDO_OPT='-I "C:\Program\ Files\mylib"'
19:29
timo oof :) 19:31
ugexe fwiw i don't think you'd typically use a non breaking space if you are quoting the path 19:33
lizmat well, yeah, but to (re-)implement complete quote handling in nqp feels... meh 19:35
ugexe that being said i dont think there is any harm in that change, just that we shouldnt expect users to just do it that way
yeah although i imagine there has to be other areas where we are splitting on spaces like this that could benefit from a generalized utility function 19:36
arguably the parsing CU::RR uses, although that is for splitting on , 19:37
lizmat yeah, but CU::RR can do that in Raku, this would have to be done in nqp 19:38
ugexe anyways im not sure how much effort it is worth to fix that issue. a comment or something that notes the flaws that someone else may wish to fix in the future would probably be sufficient for now 19:46
i.e. something that keeps someone in the future from encountering that code and wondering if the design is intentional 19:47
21:33 patrickb left, patrickb joined
ugexe why does the rakudo_opt code need to be in nqp? 22:02
timo can't compile and run raku code before the raku compiler object is done, but the rakudo opt stuff is meant to change how the compiler object behaves right? 22:07
22:09 guifa joined