🦋 Welcome to the MAIN() IRC channel of the Raku Programming Language (raku.org). Log available at irclogs.raku.org/raku/live.html . If you're a beginner, you can also check out the #raku-beginner channel!
Set by lizmat on 6 September 2022.
Nemokosch1 you know... it's just insane. Any time I look up the word "bikeshedding" on the old IRC, there is good chance the "name saga" will come up as a topic... 00:03
ngl I must admire the sole fact that it's basically the people who didn't support the renaming are the ones who basically persist to this day, having swallowed this "bitter pill" 00:07
s/are//
Nemokosch1 I only wanted to open a broad issue about flatmap and now I have crippling depression from reading IRC logs 00:12
leont Nemokosch: can I help? 00:19
Nemokosch Wait for it... almost done :) 00:22
Nemokosch The other thing I feel is that there was indeed an era of early Christmas days (years, rather) when many then-core members felt an urge to just change things 00:35
almost feels like for the sake of changing things
leont: github.com/Raku/problem-solving/issues/351 please check it out 00:41
writing a comment to take a stance 00:43
Nemokosch m: flat.map: { 1, 2 } 01:10
camelia ( no output )
Nemokosch oops
m: say flat.map: { 1, 2 }
camelia ()
Nemokosch okay, so... what happened here? xD
as opposed to: 01:11
m: say flat .map: { 1, 2 }
camelia (1 2)
Nemokosch the irony...
okay, found it. Still though :D 01:12
Nemokosch so yeah, I find it funny that the same people who argued that .flatmap is redundant and confusing, went on to provide flat map ..., flat .map(...) kind of equivalents, thereby illustrating redundance as a virtue and actually confusing code 01:29
Geth doc/document-are: 4 commits pushed by (Elizabeth Mattijsen)++ 10:00
lizmat__ argh, the wrong branch
Geth doc: 7b6f23e869 | (Elizabeth Mattijsen)++ | doc/Language/phasers.pod6
Fix typo in c<>
10:01
linkable6 Link: docs.raku.org/language/phasers
Nemokosch Apropos, and also back to what I asked yesterday... pod6. I'm considering the use of pod6 for writing these massive issue descriptions on JS. Asking the people who use pod6 regularly: how would you go about it? Is it a good idea? 11:39
Apropos, and also back to what I asked yesterday... pod6. I'm considering the use of pod6 for writing these massive issue descriptions on GH/ (chances are I'm tired). Asking the people who use pod6 regularly: how would you go about it? Is it a good idea?
Apropos, and also back to what I asked yesterday... pod6. I'm considering the use of pod6 for writing these massive issue descriptions on GH. Asking the people who use pod6 regularly: how would you go about it? Is it a good idea?
(apparently the bot triggers on edits) 11:40
lizmat yes it does 11:41
Nemokosch anyway, the question stands ^^ I'm trying to not overkill the problem, just connect my curiosity of pod6 with a more streamlined issue format for myself in the first place 11:45
guifa Nemokosch: I was I could contribuet more there. I've admittedly only dipped my toes into pod6. I'm super guilty of the getting stuff to work before documenting 13:45
tellable6 guifa, I'll pass your message to Nemokosch
guifa I'm writing a helper script to aid debugging of a module that I think could be useful to folks 14:10
but naming it is bad. It's to search for a binary sequence and binarysearch is such a misnomer haha
Nemokosch what does "search for a binary sequence" even mean here? 14:14
guifa really I guess finding a byte sequence 14:17
or doing a search in binary mode rather than in text mode
guifa is somehow having a bad link between some data and offsets, but debugging that isn't super pleasant
Nemokosch how is this used? 14:18
guifa so the helper script will take a file and a sequence of data and find all instances of that (grep-like style), and output the offset, along side the found sequence highlighted with a few bytes of data before and after to put it in context 14:19
like thinking textwise I'd do
binarysearch abcdefabcdef efa 14:20
output would be
4 cd EFA bc
lizmat guifa: maybe I should integrate the engine into App::Rak ? 14:21
guifa lizmat ooh that does sound like something that could be good in there. Let me toy around with mine and then feel free to steal as much as you want :-) 14:22
lizmat will do! :-) 14:23
Geth advent: 7109a5beb6 | (Jonathan Worthington)++ (committed using GitHub Web editor) | raku-advent-2022/authors.md
Sign up for an advent article
14:34
advent: 80b1bfff20 | (Jonathan Worthington)++ (committed using GitHub Web editor) | raku-advent-2022/authors.md
Correct typo in advent article name
Nemokosch jnthn++ 😋 14:37
leont I don't know who pheix is, but "yet another TAP harness" gets me curious 14:54
Anton Antonov @leont You are too nice... or fearless... 15:01
guifa ugh 16:29
I think this might actually be a bug in buf handling 16:30
lizmat ?
guifa so testing this search function with a four byte needle 16:31
sub is do-search($haystack, $needle) { … } 
if I immediately print the needle, it shows up as four bytes
but later on in the function, it's transformed magically to a two byte needle, but I never reassign anywhere
lizmat interesting 16:32
can you golf that ?
guifa Let me see if I can
okay nm I'm an idiot and left a debug code somewhere 16:38
lizmat *phew*
Geth Raku-Steering-Council: codesections++ created pull request #51:
Add response option: ≤ 48hr ban by one CAT member
16:56
Nemokosch It would be so good to see Daniel with regards to anything that isn't just CAT... 17:06
guifa WOW 17:13
I've literally spent like 10 days debugging this thing
and it's all because somewhere along the way I managed to zero out a dynamic variable, and so the reason my binary data files seemed off is that they WERE NEVER UPDATED
lizmat yuk
guifa on the other hand, I have a nifty little binary grepper function
imgur.com/a/9TDTNDQ 17:15
lizmat: what do you think?
lizmat looks cool 17:16
jast I once spent two weeks of debugging to finally realize there was an extra comma in my code that one particular implementation silently failed on (this was not Raku, obviously) 17:19
guifa jast: ouch
jast but it's still great when you finally find an issue like that :) 17:20
guifa not to delete the ungodly number of lines of debug code that were for naught
jast hahaha
still better than not finding the problem at all
great example of how assumptions ("everything else probably works") will sometimes end up wasting more time than checking them (and of course sometimes you're not even fully aware of the assumption in question...) 17:24
Nemokosch Very accurate 17:27
Geth Raku-Steering-Council: codesections++ created pull request #52:
Add CAT membership & update ToC
17:32
Raku-Steering-Council/main: ec465c0ecb | (Daniel Sockwell)++ | 4 files
Add CAT membership & update ToC

This adds a list of current CAT members and updates the ./papers README's ToC. It also deletes the CoC.md, which was added for rendering purposes but (I believe) isn't needed anymore.
Raku-Steering-Council/main: 3babdea3ba | (Daniel Sockwell)++ (committed using GitHub Web editor) | 4 files
Merge pull request #52 from codesections-forks/Papers

Add CAT membership & update ToC
17:33
Geth Raku-Steering-Council/main: fad631df4f | (Daniel Sockwell)++ (committed using GitHub Web editor) | README.md
Add link to Papers
18:38
Geth Raku-Steering-Council/main: 6a511f1d92 | (Daniel Sockwell)++ (committed using GitHub Web editor) | papers/code_of_conduct.md
redeploy
18:44
Geth Raku-Steering-Council: codesections++ created pull request #53:
Fix links to CoC
19:08
Raku-Steering-Council/main: ebcd4ebcca | (Daniel Sockwell)++ | 4 files
Fix links to CoC

Previous links were not rendering; I believe because they were conflicting with the *theme*'s Code of Conduct file.
19:09
Raku-Steering-Council/main: d1217017f3 | (Daniel Sockwell)++ (committed using GitHub Web editor) | 4 files
Merge pull request #53 from codesections-forks/CoC-link

Fix links to CoC
Geth Raku-Steering-Council/main: 2100d0640d | (Daniel Sockwell)++ (committed using GitHub Web editor) | papers/code_of_conduct.md
Prevent broken links to prior page
19:36
melezhik . 20:04
avuserow Is there more documentation on what MAIN subs understand? I'm looking to see if hashes can be passed somehow 20:05
melezhik .tell avuserow I see first successful builds for audio-taglib - github.com/avuserow/raku-audio-tag...1312149146
tellable6 melezhik, I'll pass your message to avuserow
avuserow I see docs.raku.org/language/create-cli but it seems to be lacking some things, for instance the --/foo form for negated boolean arguments
Demos[m] I'm confused about how export packages work 21:12
like if I _only_ define `my package EXPORT::DEFAULT {}` then things work, but `Whatever::.perl` doesn't show any `EXPORT` package like if I use `is export` 21:13
oh 21:15
it has something to do with how I'm trying to re-export
like I'm doing... (full message at <libera.ems.host/_matrix/media/v3/d...e4e0e>) 21:17
melezhik I've added GoLang support to SparrowCI pipelines (WIP, but  the major part of  API is implemented ) - twitter.com/melezhik2/status/15911...76/photo/1 21:36
now users can write Sparrow tasks in golang, no compilation is required SparrowCI will do it on the fly 21:37
pipeline example of interacting Raku and Golang task is here - github.com/melezhik/SparrowCI/blob...task2.yaml 21:38
once tasks is compiled into a binary , it's not going to be recompiled next time, so this should be pretty fast 21:40
underlying API is documented here - github.com/melezhik/sparrowgo 21:42
Demos[m] also are use and need actually equivalent? 21:57
if I have unit packages with the same name in multiple compunits and "need" them from a root unit module compunit (also the same name) then `use Module` does not import the package's exports while `need Module; import Module;` does 21:58
sorray use and `need; import`
guifa `use Foo` should get you the same results as `need Foo; import Foo` 22:32
Demos[m] it doesn't
it seems like `import` looks at the EXPORT package in whatever you point it to 22:33
while `use` only looks at the export package in the compunit you hand it
guifa so let me first make sure I understand what you're trying to do. 22:35
You've got module Foo, let's say, with several symbols that it exports 22:36
guifa then you've got a module Bar, that you want to have export several symbols that module Foo has 22:36
correct?
Demos[m] I have a module Foo, and several packages, in their own compunits, also named Foo
I ended up getting things working, the Foo module needs to look like:... (full message at <libera.ems.host/_matrix/media/v3/d...efd78>) 22:37
* I ended up getting things working, the Foo module needs to look like:... (full message at <libera.ems.host/_matrix/media/v3/d...820b9>) 22:38
or `UNIT::EXPORT::.merge-symbols(Foo::EXPORT::)
* or `UNIT::EXPORT::.merge-symbols(Foo::EXPORT::)`
Nemokosch I feel this is out of reach for me. Somebody like ugexe might know, though 23:12
avuserow: you know, the funny thing is that docs.raku.org/routine/MAIN#bundling does imply this behavior in the slightest and most subtle way 23:13
-/a is used as an example for "negating single letter arguments" 🤯 but you wouldn't see --/foo anywhere in the docs 23:15