🦋 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.
b7j0c since the name change to "raku", is the `use v6` pragma still required? or is there a new pragma? 00:04
[Coke] it was always optional. 00:08
if you specifically want v6.c or v6.d, use it - otherwise, you get the latest version of language supported available. 00:09
b7j0c awesome, thanks!
Geth ecosystem: 1373ff1901 | (Daniel Sockwell)++ | META.list
Add Pod::Tangle

URL: github.com/codesections/pod-tangle		 06:47
ecosystem: d255ad1906 | (Juan Julián Merelo Guervós)++ (committed using GitHub Web editor) | META.list
Merge pull request #539 from codesections-forks/pod-tangle

Add Pod::Tangle Again, it's GTK::Simple failing, a dependency of Raku::Pod::Render. I've created an issue asking to eliminate that. Thanks for your new module.
Xliff SUCK IT, PYTHON! repl.it/@Xliff/TechnologicalTricky...#main.raku 07:04
Bwahahahahahaaaa!
cpan-raku New module released to CPAN! App::Mi6 (1.0.4) by 03SKAJI 08:04
jmerelo Hey 08:07
rindolf jmerelo: hi, sup? 08:10
jmerelo rindolf: same old, same old... trying to address an issue in documentation and falling into a rabbit hole... 08:21
rindolf jmerelo: ah, good luck 08:22
jmerelo m: class Foo { submethod bar { &?ROUTINE.^name } }; say Foo.bar 08:23
camelia Submethod
jmerelo rindolf: thanks :-) 08:28
MasterDuke codesections: i was sort of surprised to see no mention of jupyter notebooks in your blog post 08:32
Geth doc/master: 5 commits pushed by (JJ Merelo)++ 09:28
Xliff codesections: Love your latest blog post! 09:30
Geth ¦ problem-solving: JJ assigned to jnthn Issue Ecosystem name resolution (or squatting) problem github.com/Raku/problem-solving/issues/229 09:44
Xliff m: .say for Int.^methods( *.package ) 10:11
camelia Too many positionals passed; expected 2 arguments but got 3
in block <unit> at <tmp> line 1
Xliff m: .say for Int.^methods.map( *.package )
camelia (Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Int)
(Real)
(Real)
(Real)
(Real)
(Real)
(Real)
(Real)
(Rea…
Doc_Holliwood m: ' ' ~~ rx:s/ / 10:27
is the bot down? 10:28
Doc_Holliwood thanks botmaster =) 10:29
m: ' ' ~~ rx:s/ /
evalable6 (exit code 1) 04===SORRY!04=== Error while compiling /tmp/ZenbPRLwCg
Null regex not allowed
at /tmp/ZenbPRLwCg:1
------> 03' ' ~~ rx:s/ 08⏏04/
Doc_Holliwood why dows this die? it's not a "null regex" when :s is active, right? 10:30
Xliff How would one call the "handles" trait mod in code? 10:31
lizmat trait_mod:<handles>(parameters) ? 10:32
lizmat Doc_Holliwood: feels like a bug 10:32
Geth ¦ problem-solving: holli-holzer assigned to jnthn Issue rx:s/ / is considered a null regex github.com/Raku/problem-solving/issues/230 10:55
Xliff gist.github.com/Xliff/b27f77e33539...9c28c4ed68 11:36
Doc_Holliwood I wish I could write better 13:09
I have no idea how to put a coherent text together and convey my ideas in prose 13:10
Juerd There are a gazillion books about that, many of which by authors who probably could have used some of the better books themselves :) 13:25
moritz IMHO the only remedy is practice 16:43
with occasional feedback, if you can get some
(yes, reading up on good writing is also good, but it doesn't stick without actually doing it)
codesections m: use Test; ok(False,'#') 17:49
camelia not ok 1 - \#
# Failed test ' \#'
# at <tmp> line 1
codesections Why does ^^^^ print with the `#` escaped?
moritz codesections: because # in TAP output starts a comment 17:50
so # in test descriptions need to be escaped to not be interpreted as a comment
codesections moritz++ thanks
moritz (not so relevant for visual output, but there are tools that parse TAP and put it into DBs, hilight for HTML etc.) 17:51
Geth doc: eb4828db90 | Coke++ | doc/Type/Submethod.pod6
Use spelling for this we already had
 19:50
doc: ee8c0fba67 | Coke++ | xt/pws/code.pws
new word in code block
linkable6 Link: docs.raku.org/type/Submethod 19:51
discoD hello. I've written docs for a library I want to submit, but I'd like to take a crack at writing some of it as POD. If someone could recommend a module with well-written POD to use as an example, I'd appreciate it. I don't care if it's your own. 20:15
Xliff m: use Test; ok(False,'\#') 20:25
camelia not ok 1 - \ \#
# Failed test '\ \#'
# at <tmp> line 1
Xliff m: use Test; ok(False,'##')
camelia not ok 1 - \# \#
# Failed test ' \# \#'
# at <tmp> line 1
Xliff moritz: So how do I get a naked '#' when using Test?
moritz Xliff: what do you need a naked # for? 20:27
you can emit comments (starting with #) with diag 20:28
m: use Test; diag('oh noez');
camelia # oh noez
moritz or, you know, say '#'
Xliff moritz: Well, something like this, for example... 20:29
m: use Test; ok(True,'Test #1 successful')
camelia ok 1 - Test \#1 successful
Xliff It just doesn't have the right flair any other way. :p
codesections m: use Test; ok(True, 'md lvl 4 header: #### Title') 20:31
camelia ok 1 - md lvl 4 header: \# \# \# \# Title
Xliff codesections: That was my thought, too. But nooOOoo...
codesections Xliff: no, I knew that wouldn't work -- I was agreeing with you about it being annoying. That seems like an *especially* bad set of output. 20:32
the `####` becomes basically unreadable 20:33
Xliff Yep
m: use Test; ok(True,'Test #=1 successful')
camelia ok 1 - Test \#=1 successful
Xliff m: use Test; ok(True,'Test =#1 successful') 20:34
camelia ok 1 - Test = \#1 successful
Xliff There should be a way of escaping that.
Just sayin...
codesections m: ok(True) ?? note("Test #1 sucessfull") !! note("Test #1 failed") 20:36
camelia 5===SORRY!5=== Error while compiling <tmp>
Undeclared routine:
ok used at line 1
codesections m: use Test; ok(True) ?? note("Test #1 sucessfull") !! note("Test #1 failed") 20:37
camelia ok 1 -
Test #1 sucessfull
codesections That _kind of_ works. Except for the newline. And the fact that it's clunky
Xliff codesections: Yeah, that is. Thanks for the workaround, though! 20:40

Powered by Cro and the Raku® Programming Language.

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

Thank you!