🦋 Welcome to Raku! raku.org/ | evalbot usage: 'p6: say 3;' or /msg camelia p6: ... | irclog: colabti.org/irclogger/irclogger_log/raku
Set by ChanServ on 14 October 2019.
MitarashiDango[m I don't know about rakudo-star itself, but it seems /usr/share/perl6/site/bin is empty on the Docker image D: 00:48
timotimo that's where modules get installed to, isn't it? 00:52
i mean, the binary scripts from modules
MitarashiDango[m Yup
timotimo you're expecting to find zef in there? 00:53
MitarashiDango[m Yeah zef, prove6 etc 00:55
timotimo i haven't used the docker image in ages :|
MitarashiDango[m I think there might be something wrong with the 2020.10 star tar, there's no Configure.pl 00:57
timotimo wow, whoops 00:59
where did you grab it from?
MitarashiDango[m rakudo.org/dl/star/rakudo-star-2020.10.tar.gz 01:00
timotimo yeah that looks like a tar ball from the repository that has the tools to build a rakudo star release 01:01
not an actual rakudo star release
MitarashiDango[m I think 2020.05 might also be the same 01:02
2020.01 looks to be fine though 01:03
tyil MitarashiDango[m: ./bin/rstar install [-p /path/to/install/to] 08:27
did you read the README.md?
cpan-raku New module released to CPAN! Hash::Merge (2.0.0) by 03TYIL 08:38
Geth doc/curupdir-update: 0042ae2143 | (Stoned Elipot)++ | doc/Type/IO/Spec/Unix.pod6
Update IO::Spec::Unix.curupdir for Rakudo 2020.06
 09:39
doc: stoned++ created pull request #3691:
Update IO::Spec::Unix.curupdir for Rakudo 2020.06
Geth doc: 60b367c2b5 | (Stoned Elipot)++ (committed by Juan Julián Merelo Guervós) | doc/Type/IO/Spec/Unix.pod6
Update IO::Spec::Unix.curupdir for Rakudo 2020.06
 09:54
linkable6 Link: docs.raku.org/type/IO::Spec::Unix
MitarashiDango[m tyil I was reading the instructions on rakudo.org/star/source / using p6env. I'll take another look 11:15
tyil ah, I have not rewritten the docs on the site
easy enough to do 11:16
tib Hello, I have a strange behaviour playing with arrays append and array copy. "Strange" because I don't understand :D and it is even not the same behaviour depending the run. Tested on my computer with raku 2020.10 and on repl.it. 11:26
I'm a beginner, so maybe I'm doing something totally wrong
Here is the code : gist.github.com/thibaultduponchell...e76c62a10c
tib somebody have an idea ? thank you in advance for the kind review 11:29
MitarashiDango[m I've created a PR for the docker images, it seems PATH is missing some key dirs: github.com/Raku/docker/pull/36 12:18
MitarashiDango[m tib: I highly suspect the binding is the culprit `@a := @b`, but I don't know enough about bindings to give you a decent explanation. I suspect using `@a = @b` instead should solve the problem (which should actually copy the array, rather than making @a and @b the same thing), and hopefully someone else can chime in on the why. 12:42
tobs tib: I suspect a bug. On my system I get growing arrays up until around size 400 or so and then both are constant 2. 13:03
running it with MVM_SPESH_DISABLE=1 has both grow up to 1000 elements, as, I think, intended 13:04
tib: I think that's enough evidence for a bug report.
tib Ok thank you both 13:09
Geth doc: 12fc4357b8 | (Stoned Elipot)++ | doc/Type/IO/Spec/Unix.pod6
Fix link to IO::Spec documentation
 13:11
linkable6 Link: docs.raku.org/type/IO::Spec::Unix
MitarashiDango[m I don't quite understand the behaviour of a trailing declarator block (#=) on attributes. It gets confusing if you have a conditional default. For example, if you give the attribute a default via a ternary operator, the #= has to come before the semicolon: repl.it/@mienaikage/WorthlessBelovedScandisk 15:01
Similar behaviour if you do something like = do if {...} 15:02
tib I opened an issue on MoarVM repo 16:44
github.com/MoarVM/MoarVM/issues/1381
because of the MVM_SPESH_DISABLE=1 that inhibits the issue 16:45
Doc_Holliwood m: my @s = Set.new(1,2), Set.new(2,2), Set.new(1,2); say @s.classify({$_}) 16:46
camelia {Set(1 2) => [Set(1 2) Set(1 2)], Set(2) => [Set(2)]}
Doc_Holliwood m: my @s = Set.new(1,2), Set.new(2,2), Set.new(1,2); say @s.classify(*)
camelia Doesn't make sense to classify with itself
in block <unit> at <tmp> line 1
Doc_Holliwood it seems to think whatever here refers to @s
is that supposed to happen?
lizmat Seems hardcoded that way: 16:47
multi method classify(Whatever) {
die "Doesn't make sense to classify with itself";
}
bfbf8335b6 seems the relevant comit 16:48
linkable6 (2015-05-24) github.com/rakudo/rakudo/commit/bfbf8335b6 Add some sanity to Any.(classify|categorize)
Xliff \o 16:56
Xliff pokes AlexDaniel 16:57
Xliff MitarashiDango[m: That looks like a parser error. It might be worth a bug report 17:03
gfldex lolibloggedalittle: gfldex.wordpress.com/2020/11/15/pa...el-errors/ 17:39
jmerelo releasable6:status 17:56
releasable6 jmerelo, Next release in ≈6 days and ≈1 hour. 5 blockers. Changelog for this release was not started yet
jmerelo, Details: gist.github.com/a2d9a8a916ab5ea51d...82be15f21f
Geth_ doc/io-spec-star-intro: 7cf993d3e7 | (Stoned Elipot)++ | 3 files
Fix IOC::Spec::* parent class

While here uniformize introduction to these classes		 17:57
doc: stoned++ created pull request #3692:
Fix IOC::Spec::* parent class
Geth_ doc/init-versioning: 1f53294fbe | Altai-man++ | 10 files
This introduces a way to mark versioned paragraphs

Right now configuration of paragraphs is ignored by most tools, but such metadata creates an opportunity for tools to render these blocks in a clear way, stating this is a versioned thing.
This is a first, but big step towards closing of github.com/Raku/doc/issues/302		 18:38
Geth_ doc: Altai-man++ created pull request #3693:
Introduce a way to mark versioned paragraphs		 18:50
lizmat S12 19:04
Geth_ doc: dumarchie++ created pull request #3694:
Document behavior of the + slurpy		 19:25
Geth_ doc/io-spec-star-intro: 07349367eb | (Stoned Elipot)++ | doc/Type/IO/Spec/Cygwin.pod6
Fix pasto in class name
 19:28
doc/io-spec-star-intro: e66fb29747 | (Stoned Elipot)++ | 5 files
Minimize repetition in IO::Spec::*

Add a specific section in IO::Spec document with caveats about its sub-classes. Replace these caveats's mentions in IO::Spec::* documents by a reference to IO::Spec document.
Geth_ doc: e3913c8dc0 | (Peter du Marchie van Voorthuysen)++ (committed by Juan Julián Merelo Guervós) | 2 files
Document slurpy with a bare plus sign
 19:34
doc: f779810766 | (Stoned Elipot)++ (committed by Juan Julián Merelo Guervós) | doc/Type/Supply.pod6
Add Supply.rotate
 19:35
linkable6 Link: docs.raku.org/type/Supply
guifa Assuming there’s no weird dependencies, is there any advantage or disadvantage to combing classes into a single file or unit’ing them all? 19:36
MasterDuke i believe they'll compile faster as a single file, but that's a compiler implementation thing, not a language thing 19:39
guifa And for a module that’s goign to be precompiled anyways, probably not an issue either 19:41
I have several dozen little subclasses for the different CLDR elements, and now that I’ve started adding serialization code and have to special handle them all, each class is starting to get rather unwieldy 19:43
So I think I’m goign to break them up, which should probably help me in producing cleaner documentation for them anyways
Geth_ doc: fdd9a4194b | (Stoned Elipot)++ (committed by Juan Julián Merelo Guervós) | 3 files
Fix IOC::Spec::* parent class

While here uniformize introduction to these classes		 19:44
doc: 1b4dae175e | (Stoned Elipot)++ (committed by Juan Julián Merelo Guervós) | doc/Type/IO/Spec/Cygwin.pod6
Fix pasto in class name
linkable6 Link: docs.raku.org/type/IO::Spec::Cygwin
doc: c30beeb53f | (Stoned Elipot)++ (committed by Juan Julián Merelo Guervós) | 5 files
Minimize repetition in IO::Spec::*

Add a specific section in IO::Spec document with caveats about its sub-classes. Replace these caveats's mentions in IO::Spec::* documents by a reference to IO::Spec document.
rir How to tell if an rakudo install is rakudo star? 20:29
guifa rir: I don’t think you can tell per se from a script. Rakudo star is a just a distribution that includes MoarVM, Rakudo, and some key modules. I guess you could check the version/build numbers of each and reasonably determine it, knowing each star release’s info 20:43
rir guifa, thanks. 20:58
AlexDaniel` Xliff: yes? 23:30
ah, I see the message now :) 23:31

Powered by Cro and the Raku® Programming Language.

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

Thank you!