00:04 |Tux| left 00:30 atta joined 00:32 atta left 00:42 sena_kun left 00:56 sena_kun joined 01:09 |Tux| joined
AlexDaniel moritz: I don't want to be running in circles later when I'd need to tweak something 01:47
jnthn: then what about this (it's an old channel, and TimToady doesn't have the same privs on #perl6 anyway): flags #perl6-dev TimToady -F 01:50
jnthn: also please let me know who should have +F on #raku and #raku-dev, currently it's just me and mst
well, I guess you should : 01:51
:)
done 01:52
Geth_ nqp/master: 6 commits pushed by (Daniel Green)++, MasterDuke17++ 01:57
AlexDaniel interesting, there does not seem to be a real limit for org invitations 02:22
let's see if it gets me banned :) 02:23
vrurg "I'd jump from a cliff. Let's see if I survive..."?? ;) 02:25
AlexDaniel vrurg: it's an alright sacrifice, if I survive everyone gets invited to Raku org : 02:26
:)
without me having to run it every day for a week
02:27 |Tux| left
vrurg I was and have accepted already. 02:27
BTW, shall I migrate nqp-configure meanwhile?
AlexDaniel no 02:28
well… let's wait a bit
“302 pending invitations”
vrurg: one issue we've seen with the too early doc repo move was that all assignments were gone 02:29
because you can't be assigned unless you're part of the org
… or have the privileges in some other way, but you get the point
vrurg Oh, sure...
AlexDaniel so ideally we should wait for people to accept the invites, and then we can move 02:30
vrurg Ok, can wait for until most people accepts the invitations and other things are settled down.
AlexDaniel of course not everyone will accept them in a timely manner, but let's at least wait a few days…
vrurg For a month or two if necessary.
02:30 |Tux| joined
AlexDaniel well, I just want the most active users to accept :) 02:30
vrurg Best if it would be possible to determine that unaccepted ones are the most long inactive ones. 02:31
Ok, we think almost synchronously. ;)
AlexDaniel vrurg: btw can you check github.com/Raku/p6rt/issues?q=is%3...s%3Aclosed ?
see if things make sense to you 02:32
though I guess you didn't use RT much
vrurg More like I never used whatsoever.
I joined when GH had already like 800 open issues. 02:33
vrurg is half-away committing a fix for attribute accessors.
AlexDaniel alright :)
squashable6: status
squashable6 AlexDaniel, ⚠🍕 Next SQUASHathon in 1 day and ≈1 hour (2020-01-04 UTC-12⌁UTC+20). See github.com/rakudo/rakudo/wiki/Mont...Squash-Day
AlexDaniel mmm there's no good way to cancel a squashathon :D 02:34
if I set the date to 2020-01-01 it'll become active…
02:36 travis-ci joined
travis-ci Rakudo build failed. Elizabeth Mattijsen 'Split Supply.unique into 2 multi's 02:36
travis-ci.org/rakudo/rakudo/builds/631648623 github.com/rakudo/rakudo/compare/8...8cfef3899b
02:36 travis-ci left 02:42 sena_kun left
Geth_ roast: rbt++ created pull request #609:
Enable nanosecond times		 02:50
rakudo: rbt++ created pull request #3396:
Allow DateTime to nanoseconds.		 02:51
rakudo: vrurg++ created pull request #3397:
Prioritize class attributes/method over those from roles		 02:52
rakudo: rbt++ created pull request #3398:
Correct URL in readme		 02:54
roast: vrurg++ created pull request #610:
Add tests for class stuff prioritzing over role's		 02:57
02:58 sena_kun joined
vrurg Appveyor is broken because can't fetch strawberry... :( 03:14
Geth_ rakudo: 2463777268 | (Rod Taylor)++ | README.md
Correct URL in readme.
 03:22
rakudo: f00a9fc99e | (Vadim Belman)++ (committed using GitHub Web editor) | README.md
Merge pull request #3398 from rbt/f.readme

Correct URL in readme
toddr So there are about 300 migrated RT issues you guys can look at at here github.com/Raku/p6rt/issues 03:41
If you're ok with them, I'm ready to migrate everything. It should only take a couple of hours and then robert will finalize the re-directs. 03:42
AlexDaniel toddr: so, what about labels? :) 03:54
colabti.org/irclogger/irclogger_lo...-01-01#l40
toddr I'm happy to label based on some trait in the ticket.
what is it you want labeled? 03:55
AlexDaniel toddr: I mean the [ ] in ticket titles
toddr I didn't find extensive use of labels like perl5 did
it's actually easier to migrate them then search for [BUG] and label them all if everything is in the title 03:56
but lemme look at the titles. how many labels are we talking about?
AlexDaniel if you look here you'll see some numbers: web.archive.org/web/20181121184441...udo.party/ 03:57
toddr and all of these are in the subject of the RT? 03:58
that should be easily done.
do you want me to take it out of the subject if I'm labeling the tickets?
AlexDaniel toddr: yes and yes 04:05
if it's not too hard : 04:06
:)
toddr ok the biggest problem will be getting the full label list. gimme a few 04:12
How should the labels be? PATCH, patch, Patch ? 04:15
you can rename them later but better to do it right from the start 04:16
AlexDaniel toddr: all lowercase is fine 04:22
toddr ok
AlexDaniel toddr: this is a weird ticket: github.com/Raku/p6rt/issues/248 04:24
I wonder what was there originally
toddr click through and look?
AlexDaniel that's a new website, not RT 04:25
toddr rt.perl.org/Public/Bug/Display.html?id=57986
AlexDaniel ah, there
toddr GIGO :D
AlexDaniel ok, well, then it's correct :)
toddr: thank you for working on this
toddr np 04:26
04:42 sena_kun left 04:57 sena_kun joined 05:57 evalable6 left 06:00 evalable6 joined 06:42 sena_kun left 06:51 travis-ci joined
travis-ci Rakudo build passed. Vadim Belman 'Merge pull request #3398 from rbt/f.readme 06:51
travis-ci.org/rakudo/rakudo/builds/631733085 github.com/rakudo/rakudo/compare/d...0a9fc99e3d
06:51 travis-ci left 06:55 Xliff left 06:57 sena_kun joined 07:20 Tux__ joined 07:23 [TuxCM] left 07:35 [TuxCM] joined 07:36 Tux__ left 08:11 sena_kun left 08:12 sena_kun joined 08:24 [TuxCM] left 08:42 sena_kun left 08:55 sena_kun joined
lizmat Files=1294, Tests=109633, 211 wallclock secs (28.58 usr 8.22 sys + 2966.97 cusr 272.60 csys = 3276.37 CPU) 10:04
10:15 timotimo left
bartolin .tell vrurg If you have some spare minutes, maybe you could take a quick look at github.com/rakudo/rakudo/issues/3399? I'm still searching for a fix, but I'm mostly in the dark. Maybe you have a quick idea and can give me a pointer in what direction to look. 10:24
tellable6 bartolin, I'll pass your message to vrurg
10:27 |Tux| left
Geth_ rakudo: cde92b4974 | (Elizabeth Mattijsen)++ | 3 files
Modernize extension of snapper.pm6
 10:34
10:35 sena_kun left
Geth_ rakudo: 09f349a804 | (Elizabeth Mattijsen)++ | 3 files
Modernize extension of Telemetry.pm6
 10:36
10:39 bartolin left, camelia left
Geth_ rakudo: 13e3419905 | (Elizabeth Mattijsen)++ | 3 files
Modernize extension of experimental.pm6
 10:42
10:47 bartolin joined
Geth_ rakudo: 59e70e950b | (Elizabeth Mattijsen)++ | 3 files
Modernize extension of MoarVM/Profiler.pm6
 10:47
rakudo: 72bbc5832b | (Elizabeth Mattijsen)++ | 2 files
Modernize extension of Spesh.pm6
 10:48
10:49 camelia joined 10:50 sena_kun joined
Geth_ rakudo: e0b29370f6 | (Elizabeth Mattijsen)++ | 3 files
Modernize extension of newline.pm6
 10:56
rakudo: 5197952658 | (Elizabeth Mattijsen)++ | 3 files
Modernize extension of Test.pm6
 11:02
¦ problem-solving: lizmat assigned to jnthn Issue Generalization of the "settings" concept github.com/perl6/problem-solving/issues/143 11:03
11:07 |Tux| joined
Geth_ rakudo: 1e316db362 | (Elizabeth Mattijsen)++ | 3 files
Modernize extension of CompUnit/Repository/Staging.pm6
 11:11
rakudo: 8a0742eeb3 | (Elizabeth Mattijsen)++ | 3 files
Modernize extension of Pod/To/Text.pm6
 11:17
11:37 Kaiepi joined
|Tux| Rakudo version 2019.11-338-g8a0742eeb - MoarVM version 2019.11-103-g2ac1fa27f
csv-ip5xs0.762 - 0.770
csv-ip5xs-206.439 - 6.673
csv-parser38.884 - 40.324
csv-test-xs-200.418 - 0.431
test7.348 - 7.698
test-t1.766 - 1.826
test-t --race0.797 - 0.810
test-t-2030.617 - 31.208
test-t-20 --race9.145 - 9.675
 12:24
12:42 sena_kun left 12:56 sena_kun joined
lizmat nine: please see gist.github.com/lizmat/cbd2141b4f0...80058fdc3f 13:01
isn't it strange that NativeCall/Types occurs twice in there ?
the only real difference appears to be the source-line-number ? 13:02
nine And now I know why I've never liked having source-line-number in the dependency specification. Time to throw it out 13:05
Where do we usually get the current line number from for exceptions thrown in compilation? 13:06
lizmat out of the Match object, I think ? 13:08
nine Looks like we usually declare a $*LINE_NO
lizmat nine: so you're saying this is a generic issue, and not related to my renaming extensions ? 13:10
nine yes 13:12
Can't see how that would cause any problems
13:23 lucasb joined
lizmat hmmm... indeed: in NativeCall.pm6, NativeCall:Types is use from line 4, in NativeCall/Compiler/* it is on line 3 13:28
so what does it mean to have these two entries? That it is trying to load the same precomp file for every different line number ?
and then finding out it is loaded already ?
hmm... the SHA's look identical though ? 13:29
13:33 Xliff joined
nine It will tell the store to load the unit a second time but the store will find it in the cache 13:37
lizmat yeah, so extra, unnnecessary work 13:40
changing CompUnit::DependencySpecification.perl now
nine: should version|auth|api-matcher be part of this string or not ? 13:44
feels to me it shouldn't either ?
or am I misunderstanding ?
the only thing really that's needed, is the short-name and the from ? 13:45
nine Those definitely must be there! They The whole CompUnit::DependencySpecification part is used to re-check the dependency after the repository's contents changed. This mechanism keeps us from re-compiling everything after every single module installation 13:46
lizmat ok 13:51
spectesting a change now 13:52
Geth_ rakudo: bda8dcb00a | (Elizabeth Mattijsen)++ | 2 files
Don't use .perl in serialization ID creation

The source-line of 'use' statements is part of .perl output of CompUnit::DependencySpecification, which was used to create serialization ID's stored in .precomp files. This adds a "serialization-id" method that creates a shorter, but still readable string that is actually valid Raku code, but does not contain the source-line number. This should, possibly drastically, reduce the number of attempts to load the same module.		 14:00
lizmat nine: ^^ 14:01
it also looks like this change makes the NativeCall.pm6 -> .rakumod test pass 14:10
nine lizmat: I just finished a patch that removes the source-line-number as it should never have been part of the DependencySpecification in the first place. It does not specify a dependency after all 14:13
lizmat nine: feels to me I beat you to it ?
nine Also that string is NOT intended for human consumption. It is solely used as input for EVAL. 14:14
lizmat ok, well, then my patch should also be ok :-)
why EVAL? 14:15
why not some JSON like structure ?
nine Please revert that patch. It definitely breaks things
lizmat it passed make test and make spectest and it fixed the rename issue ?
nine github.com/rakudo/rakudo/commit/bd...73075bL114
lizmat my patch produces valid Raku code 14:16
so the EVAL should work (and does afaics) 14:17
installing / uninstalling modules also works 14:18
nine Does it work with a DependencySpecification like this? CompUnit::DependencySpecification.new(:short-name<Foo>, :version-matcher(1..5.5), :auth-matcher(/foo.*bar/)) 14:19
lizmat aaah... ok 14:20
no, it wouldn't
but your patch would ?
nine If your rename issue is caused by that doubling of the dependency line, then yes 14:21
Geth_ rakudo: 037affddc2 | (Elizabeth Mattijsen)++ | 2 files
Revert "Don't use .perl in serialization ID creation"

This reverts commit bda8dcb00a53d1a194c6886dec37220887dd0f80.
  nine has a better solution
lizmat I know also see the need for EVAL :-)
perhaps get rid of the source-line completely ? 14:25
nine That's what I do 14:27
lizmat oki :-)
14:32 AlexDani` joined 14:34 AlexDaniel left 14:41 AlexDani` left 14:42 sena_kun left 14:58 sena_kun joined
vrurg bartolin: replied in the issue. Though it's not much, unfortunately. 15:07
tellable6 hey vrurg, you have a message: gist.github.com/8d889a4efe93ff53b3...39837fcafa
bartolin vrurg: thanks, anyway :) 15:09
vrurg bartolin: I'd try to have a look into it, if get some time. It feels like another problem with JVM strikes back. 15:10
nine lizmat: now that I've finished my fix, and it works and is pretty and whatever, I came across an even better solution, proposed by a certain "niner" back in October: github.com/rakudo/rakudo/issues/20...-543177164 15:33
vrurg is humbly asking nine: perhaps you'd have time to take care of circular deps too? 15:41
Geth_ rakudo/master: 8 commits pushed by (Vadim Belman)++ 15:43
roast: 92b6ff44c6 | (Vadim Belman)++ | S14-roles/attributes.t
Add tests for class stuff prioritzing over role's

Also make typeobjects from a previous test lexically-scoped.
In support of rakudo/rakudo#3382 and rakudo/rakudo#3397
roast: aae83964cd | (Vadim Belman)++ (committed using GitHub Web editor) | S14-roles/attributes.t
Merge pull request #610 from vrurg/rakudo_3382

Add tests for class stuff prioritzing over role's
16:24 AlexDani` joined
nine Turns out, we already have the whole infrastructure for reporting the location of errors. So getting that is as simple as adding a CATCH { self.rethrow($/, $_); } to Perl6::World::load_module 16:28
With this we get a message like "Could not find Foo in: ... at -e:1" 16:29
16:33 patrickb joined 16:36 AlexDani` is now known as AlexDaniel, AlexDaniel left, AlexDaniel joined 16:42 sena_kun left
nine *sigh* this runs into spec test issues. Not because it breaks anything, but because we test error messages for things we don't actually care about. 16:43
One tests the JSON exception handler's output for "X::CompUnit::UnsatisfiedDependency" when it would now read "X::CompUnit::UnsatisfiedDependency+{X::Comp}" 16:44
The other is a regression test ensuring that we don't report precompilation errors twice. But it only checks for 2 "SORRY" which trips over:
===SORRY!=== Error while compiling -e
===SORRY!=== Error while compiling /home/nine/rakudo/t/spec/packages/RT127176/lib/RT127176.pm6 (RT127176)
The thing is: I actually like that structure: it clearly shows that there are two compilation errors. The one in the module and the other in the module's user where compilation trips over not being able to load the module 16:45
This way we would actually show the whole chain of users. That does sound very useful to me as in a large code base it's often not obvious why some odd module even gets loaded. 16:48
16:56 sena_kun joined 17:00 patrickb left
bartolin vrurg: just a quick question: shouldn't the result of this nqp::findmethod be returned? github.com/rakudo/rakudo/commit/93...b24fd2R155 17:20
vrurg bartolin: good catch, of course it should! 17:48
bartolin: BTW, shall I merge the dispatch:<::> fix? 17:49
17:52 AlexDani` joined
bartolin vrurg: (merge) would be nice! 17:53
17:54 AlexDaniel left
Geth_ rakudo: 5648a4f399 | (Christian Bartolomäus)++ | src/core.c/Mu.pm6
Check type before looking for qualified method

This fixes a failing test in S12-methods/qualified.t on the JVM backend. The code in src/vm/moar/spesh-plugins.nqp does a similiar check before calling 'find_method_qualified'.
A somewhat golfed version of the failing test would be: ... (10 more lines)		 17:59
rakudo: 2a4eb56a33 | (Vadim Belman)++ (committed using GitHub Web editor) | src/core.c/Mu.pm6
Merge pull request #3394 from usev6/missing_concretization

Check type before looking for qualified method
toddr AlexDaniel: This is the list of labels. If you want the colors to be something else, let me know. 18:00
tellable6 toddr, I'll pass your message to AlexDaniel
toddr gist.github.com/toddr/9e779e61384a...a95b34bdd8
Geth_ rakudo/master: 7 commits pushed by (Vadim Belman)++ 18:02
roast/master: 4 commits pushed by (Vadim Belman)++ 18:03
18:06 patrickb joined
patrickb rba: I have created binary builds for Linux, MacOS and Windows for the rakudo 2019.11 release. They can be downloaded here: patszim.volans.uberspace.de/patclo...EJLQDZcjbf 18:07
.tell rba I have created binary builds for Linux, MacOS and Windows for the rakudo 2019.11 release. They can be downloaded here: patszim.volans.uberspace.de/patclo...EJLQDZcjbf
tellable6 patrickb, I'll pass your message to rba
patrickb .tell rba You can put them on stage-rakudo.rakulang.site/ 18:08
tellable6 patrickb, I'll pass your message to rba
patrickb .tell rba That's the last missing bit that was standing in the way of the new rakudo.org website as far as I know. 18:09
tellable6 patrickb, I'll pass your message to rba
patrickb .tell rba Some testing of those builds would be welcome of course. 18:10
tellable6 patrickb, I'll pass your message to rba
Geth_ rakudo: d9781071aa | (Patrick Böker)++ | docs/release-guide-binary.md
Minor changes to the binary release guide commands

  - don't include owners and groups in tar archives
  - make curl follow forwards (rakudo.org is currently forwarding downloads
to github)
  - use `raku` instead of `perl6`		 18:13
vrurg .ask lizmat Could you, please, have a brief look at github.com/rakudo/rakudo/pull/3396? I like it but it's more of your area than mine. 18:19
tellable6 vrurg, I'll pass your message to lizmat
lizmat vrurg: will look at it later tonight 18:24
vrurg lizmat: I can make it shorter: do you mind increasing seconds precision in DateTime to 12 digits (pico-seconds)? If no immediate answer then it can surely wait. 18:27
lizmat without changing the default formatter output? yeah, I could very well live with that :-) 18:28
vrurg Sure, I pulled the formatter back as I didn't like it too. Ok, I give it the green light. 18:29
18:42 sena_kun left
vrurg .tell Xliff BTW, you might be interested in this: github.com/rakudo/rakudo/pull/3397...b88429R122 and respectively this: github.com/rakudo/rakudo/pull/3397...efb734bR30 18:44
tellable6 vrurg, I'll pass your message to Xliff
18:58 sena_kun joined
nine Ha! The test for the JSON exception handler is not only overly specific, but also not specific enough. While it tests the generated JSON output for certain contents, it doesn't test if the output actually is valid JSON. Thus it misses the "}Saw 1 occurrence of deprecated code." at the end 19:22
Turns out, we simply cannot deprecate the PERL6_EXCEPTIONS_HANDLER environment variable, as that is covered by 6.d-errata tests. 19:23
Now the hardest part is: how can we properly test JSON output for real in roast? I'm very tempted to use Rakudo::Internals::JSON, but that's obviously LTA 19:37
Geth_ rakudo: d406d834de | (Elizabeth Mattijsen)++ | src/core.c/Mu.pm6
Make sure Mu.raku maintains containerness of invocant
 19:46
lizmat nine: using "eq" :-) 19:52
Geth_ rakudo: 62bd2743f9 | (Elizabeth Mattijsen)++ | 45 files
Use .raku instead of .perl in the setting
 19:53
dogbert11 lizmat: is t/spec/S32-num/stress.t supposed to fail some tests. I'm not sure I understood your answer the other day :) 19:59
lizmat I've not seen that fail for many months 20:00
and I run many spectests a day
e.g. for every commit I did today
dogbert11 but isn't that file part of 'make stresstest' 20:01
so perhaps it's not run as often
not ok 94 - parsed literal == val() [.73142176224725044386e235] 20:02
lizmat aaahhhh make stresstest
ok
lemme check in a few minutes 20:03
dogbert11 ++lizmat
nine lizmat: then we're back to overly specific :) 20:15
I could copy&paste the JSON::Tiny grammar: modules.raku.org/dist/JSON::Tiny:c...Grammar.pm 20:17
Geth_ rakudo: 6bf6d34701 | (Elizabeth Mattijsen)++ | src/core.c/Mu.pm6
Oops, we need to allow Mu for the invocant
lizmat nine: yeah, it wouldn't need to be fast :-) 20:18
Geth_ rakudo: e4efccc6c1 | (Elizabeth Mattijsen)++ | 6 files
Change all references of "perlseen" to "rakuseen"
 20:19
lizmat .ask moritz I thought old ircloge.perlgeek links would be redirected to colabti? 20:24
tellable6 lizmat, I'll pass your message to moritz
lizmat e.g. irclog.perlgeek.de/perl6-dev/2017-...i_14585448
or is this something rba should be made aware of ?
nine It's actually not _that_ bad: :err({ JSON::Tiny::Grammar.parse($_)<value><object><pairlist><pair>[0]<value><object><pairlist><pair>.first(*<string><str> eq 'specification')<value><string><str>.Str eq 'FakeModuleRT129810'; }), 20:27
20:42 sena_kun left 20:56 sena_kun joined 21:11 AlexDani` left, AlexDani` joined
Geth_ roast: 91fe5d9eb6 | (Stefan Seifert)++ | S10-packages/precompilation.t
Fix overly specific test for precompilation error messages

The test failed when 2 compilation errors were reported, not just when the same error was reported twice.		 21:13
roast: 379b99b33e | (Stefan Seifert)++ | S04-exceptions/exceptions-alternatives.t
Fix test for JSON exception output of module load failure

The test was overly specific as it tested the serialized JSON string for a specific class name which fails as soon as the exception gets some role mixed in. The test was also underly specific in that it didn't catch a deprecation message attached to the JSON output. Fix by using a real JSON parser.
roast/6.d-errata: 2b3f74e53c | (Stefan Seifert)++ | S10-packages/precompilation.t
Fix overly specific test for precompilation error messages

The test failed when 2 compilation errors were reported, not just when the same error was reported twice.
roast/6.d-errata: 38d56c968e | (Stefan Seifert)++ | S04-exceptions/exceptions-alternatives.t
Fix test for JSON exception output of module load failure

The test was overly specific as it tested the serialized JSON string for a specific class name which fails as soon as the exception gets some role mixed in. The test was also underly specific in that it didn't catch a deprecation message attached to the JSON output. Fix by using a real JSON parser.
rakudo: 6f527cea9a | (Stefan Seifert)++ | 3 files
Remove source-line-number from CompUnit::DependencySpecification

The source-line-number was only used for exception messages and should never have been in the DependencySpecification object as it doesn't specify a dependency. It also led to duplicated dependency lines in precomp files as the dependencies are deduplicated by the .perl output of the DependencySpecification object.
Instead, use the existing infrastructure for adding source location information to exceptions.		 21:18
rakudo: b54d83b8b5 | (Stefan Seifert)++ | src/core.c/Exception.pm6
Revert deprecation of PERL6_EXCEPTIONS_HANDLER

The PERL6_EXCEPTIONS_HANDLER environment variable is actually part of the 6.d spec, so we cannot remove it. Further the deprecation message went into the same stream as the supposedly machine readable output, potentially disrupting tools that this output was meant for.
nine lizmat: ^^^ 21:40
21:40 AlexDani` is now known as AlexDaniel, AlexDaniel left, AlexDaniel joined
lizmat whee! :-) 21:43
AlexDaniel lizmat: there's no simple mapping from perlgeek logs to colabti 21:53
tellable6 2020-01-02T18:00:06Z #raku-dev <toddr> AlexDaniel: This is the list of labels. If you want the colors to be something else, let me know.
AlexDaniel lizmat: it used to be done through a redirect service hosted by zoffix
lizmat: that went down at some point
lizmat indeed... but the underlying translation table is also lost ? 21:54
:-(
AlexDaniel no, it's somewhere
lizmat that would be meh
AlexDaniel I probably have it
lizmat ok
need to be afk atm, I'll be back later&
AlexDaniel but yeah we do need to bring it back it life
toddr I'm doing a full import to p6rt so you guys can see what it looks like at this point 22:17
1/3 done.
patrickb .tell rba The stage-rakudo.rakulang.site/dl -> github redirect seems to be active again. Can you disable that (for the staging website only) again? 22:26
tellable6 patrickb, I'll pass your message to rba
22:41 sena_kun left 22:55 sena_kun joined
Geth_ rakudo: b7888d79c8 | (Elizabeth Mattijsen)++ | src/Perl6/Metamodel/RoleToClassApplier.nqp
Two more cases of .perl -> .raku
 23:07
AlexDaniel toddr: the final one will be into the right repo, right? github.com/perl6/old-issue-tracker
23:08 Geth_ left
toddr ¯\_(ツ)_/¯ I can put it wherever. 23:08
23:08 Geth joined
toddr You cannot transfer issues to a different org 23:08
so getting them all into one org first is recommended.
also the RT re-directs will break if you later move the repo.
lizmat .tell dogbert11 S32-num/stress.t is a flapper for me 23:14
tellable6 lizmat, I'll pass your message to dogbert11
lizmat .tell dogbert11 failure is typically 1.2873811240847445e-25 vs 1.2873811240847447e-25, aka the last shown digit 23:16
tellable6 lizmat, I'll pass your message to dogbert11
lizmat .tell dogbert11 so it appears there *is* drift when roundtripping, and it is *not* load related 23:18
tellable6 lizmat, I'll pass your message to dogbert11
lizmat good night #raku-dev&
japhb o/ lizmat 23:23
23:37 Kaiepi left 23:38 Kaiepi joined

Powered by Cro and the Raku® Programming Language.

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

Thank you!