[perl #128282] Inconsistent use of snake_case and kebob-case in Test.pm6

# New Ticket Created by Zoffix Znet # Please include the string: [perl #128282] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128282 > The `is-approx` sub in Test.pm6 module has a multi that take optional rel_tol and

[perl #128285] [BUG] Circular module dependency is not detected; causes program to hang

# New Ticket Created by Sam S. # Please include the string: [perl #128285] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128285 > When two modules `use` each other, Rakudo does not throw a compile-time error as it should.

[perl #128283] [RFC] Disallow strings as ops in cmp-ok in Test.pm6

# New Ticket Created by Zoffix Znet # Please include the string: [perl #128283] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128283 > The operators for `cmp-ok` subroutine can be given as strings or as Callables. The

[perl #128284] [BUG] cmp-ok in Test.pm6 attempts to coerce the comparator to string, triggering a warning

# New Ticket Created by Zoffix Znet # Please include the string: [perl #128284] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128284 > m: use Test; cmp-ok 5, &[<], 3; rakudo-moar beb3c9: OUTPUT«not ok 1 - ␤␤# Failed test

[perl #128275] [BUG] Circular module dependency is not detected; causes program to hang

Hm you're right, predeclaration doesn't seem to be the correct solution to your problem after all. But this bug tracker is not the right place for Perl 6 user support, it should be reserved for collecting info on actual Rakudo bugs. You should ask on the #perl6 IRC channel instead, I'm sure

Re: [perl #128282] Inconsistent use of snake_case and kebob-case in Test.pm6

On Sunday, May 29, 2016, Zoffix Znet wrote: ... > I'm willing to do the work, if the proposal is accepted. The question then > becomes: should the old names stay? > I support your proposal for kebob-casing. -Tom [tbrowder]

[perl #128289] localhost in IO::Socket::INET

# New Ticket Created by mt1957 # Please include the string: [perl #128289] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128289 > Hi, A subtle problem. Golfed down to; my IO::Socket::INET $sock; $sock .= new( :host,

Re: [perl #128289] localhost in IO::Socket::INET

On Sun, May 29, 2016 at 1:43 PM, mt1957 wrote: > * On both systems localhost translates to 127.0.0.1 (checked with dig) Note that dig only tells you what DNS returns, not what a query through NSS returns; use "getent hosts" for that. In particular, it will not

Re: [perl #128289] localhost in IO::Socket::INET

On 05/29/2016 07:47 PM, Brandon Allbery via RT wrote: getent hosts > getent hosts on faulty system 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 127.0.0.1 localhost localhost.localdomain localhost6 localhost6.localdomain6 On ok system. It differs