patrickb MasterDuke: Thanks for the solo term link. That might prove helpful as a reference. 06:56
tellable6 patrickb, I'll pass your message to MasterDuke
patrickb MasterDuke: Are you aware that there already is a minimal but kinda working raku terminal emulator library? sr.ht/~patrickb/Anolis/ 06:58
tellable6 patrickb, I'll pass your message to MasterDuke
Xliff_ There's also github.com/Xliff/p6-VTE :) 08:14
lizmat notable6: weekly 12:07
notable6 lizmat, 3 notes: gist.github.com/1ea30d1aceea47843f...454016d4ad
lizmat notable6: weekly reset
notable6 lizmat, Moved existing notes to “weekly_2025-03-31T12:07:37Z”
lizmat [Coke]: re Whateverable gists: gist.github.com/Whateverable says 5000+ 12:08
[Coke] releasable6: next 12:17
releasable6 [Coke], Next release in ≈19 days and ≈6 hours. 1 blocker. 102 out of 102 commits logged
[Coke], Details: gist.github.com/5eeeabf3c2eada1207...cb7b0a4c38
[Coke] ... in private it was saying 100/102. :P
lizmat and yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2025/03/31/2025-...t-journey/ 12:25
jdv what is 209 again? 12:35
only ~20 tests in both suites to go - that's amazing 12:37
lizmat m: say (209 * 7) / 12 12:40
camelia 121.916667
lizmat m: say (209 * 7) / 365.25
camelia 4.005476
lizmat jdv: it's actually test-files, but yeah amazing! nine++ 12:42
jdv hasnt had coffee yet 12:45
nine Adding warnings about sink context reveals a few benign coding errors in the setting and also: 12:46
Useless use of .take xx ($seconds / 1e9) in sink context
Now my immediate reaction would be to not warn on a sunk xx as it obviously can have desired side effects.
But then.... it *is* an expression with a result and that result is unused. Personally I don't like this construct for this reason. 12:47
nine We e.g. have this syntax available: .take for ^($seconds / 1e9) 12:47
lizmat yeah, that's probably why it should keep this warning: so people don't use that construct
nine To me this would be more clear, that it's just a loop 12:48
JimmyZhuo at /home/jimmyz/rakudo/t/spec/integration/advent2013-day10.t:27
------> est-strings(:greet<Hello> :person«$user»⏏);
Ambiguous use of >>; use » instead to mean hyper, or insert whitespace before >> to mean a quote terminator (or use different delimiters?)
at /home/jimmyz/rakudo/t/spec/integration/advent2013-day10.t:28
------> t-strings(:greet<Hello> :person<<$user>>⏏);
...
Ambiguous use of »; use >> instead to mean hyper, or insert whitespace before » to mean a quote terminator (or use different delimiters?)
at /home/jimmyz/rakudo/t/spec/integration/advent2013-day10.t:27
------> est-strings(:greet<Hello> :person«$user»⏏);
Ambiguous use of >>; use » instead to mean hyper, or insert whitespace before >> to mean a quote terminator (or use different delimiters?)
at /home/jimmyz/rakudo/t/spec/integration/advent2013-day10.t:28
------> t-strings(:greet<Hello> :person<<$user>>⏏);
full message
lizmat m: say Q|my $a; ++$a; 42|.AST.EVAL # probably known to nine already 16:32
camelia Potential difficulties:
Useless use of $a in sink context
at EVAL_0:1
42
lizmat m: BEGIN CORE:: 16:52
camelia ( no output )
lizmat nine: put "BEGIN CORE::" in a .rakumod file, and try to load it with precompilation, and get:
Missing serialize REPR function for REPR MVMContext (BOOTContext)
legacy and RakuAST 16:53
looks like PseudoStashes need some barriers when called at compile time ?
vrurg ^^ ideas ?
nine Well a PseudoStash does store an nqp::ctx in an attribute 17:28
lizmat but UNIT:: and SETTING:: do also, and they aren't a problem for some reason 17:30
nine: the right fix would be to put nqp::scwbdisable; / nqp::scwbenable; at the right places, right? 17:32
nine Can't tell. After all then some value would not be in the precomp file and I don't know how it will cope with that 17:34
Might just push the error further down the line
lizmat well, generally we'd want a value from the PseudoStash, not the whole PseudoStash 17:37
nine Well with CORE:: you do get a PseudoStash :) 17:40
lizmat true: but that was the golf 17:56
&CORE::prompt was the original case 17:57
lizmat nine: do we have a way to find out whether we're precomping user code (as opposed to the setting itself) ? 18:23
nine $*COMPILING_CORE_SETTING? 18:24
Geth rakudo/bootstrap-rakuast: 22 commits pushed by (Stefan Seifert)++
review: github.com/rakudo/rakudo/compare/b...ca7ac09a2b		 19:48
nine bootstrap works again
finanalyst .tell [Coke] would you please look at the edit function on new-raku. 21:59
tellable6 finanalyst, I'll pass your message to [Coke]
[Coke] 145/166 (make test), and 1331/1350 (make spectest) # these still right? 22:09
(for RakuAST)

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!