[perl #132632] [POD][NYI]. List and hash configuration value formats are not yet implemented (NYI)

closed also with tests in merged roast PR #371

[perl #130477] [BUG][POD] Pod config parses colopairs but simply stringifies whatever it matched

closed also with tests in merged roast PR #371

[perl #126742] [POD] config items should not include quotes for string values

closed also with tests in merged roast PR #371

[perl #124281] colonpairs in [POD] config options always produce strings

closed also with tests in merged roast PR #371

[perl #132632] [POD][NYI]. List and hash configuration value formats are not yet implemented (NYI)

closed by merge of rakudo PR #1339

[perl #130477] [BUG][POD] Pod config parses colopairs but simply stringifies whatever it matched

closed by merge of rakudo PR #1339

[perl #126742] [POD] config items should not include quotes for string values

closed by merge of rakudo PR #1339

[perl #124281] colonpairs in [POD] config options always produce strings

closed by merge of rakudo PR #1339

[perl #128221] [BUG] Weird internal error when parsing some very simple Pod with '-' in the first column of a table in Rakudo

tests added in roast PR #353

[perl #132348] [POD] tables should accept an inline comment (Z)

tests added in roast PR #353

[perl #132348] [POD] tables should accept an inline comment (Z)

tests added in roast PR #353

[perl #124403] [POD] Table parsing broken in rakudo

tests added in roast PR #353

[perl #129862] Pod::To::Text failing on uneven row lengths

Root problem is fixed by PR #1240.

[perl #132341] [POD] table handling should ensure table rows have the same number of cells even if they are empty

Fixed by PR #1240.

[perl #128221] [BUG] Weird internal error when parsing some very simple Pod with '-' in the first column of a table in Rakudo

Fixed by PR #1240.

[perl #132348] [POD] tables should accept an inline comment (Z)

Fixed by PR #1240.

[perl #124403] [POD] Table parsing broken in rakudo

Fixed by PR #1240.

[perl #132377] [BUG][POD] tables inside =begin/=end comment pairs cause exception

On Mon, 30 Oct 2017 09:16:23 -0700, tbrowder wrote: > On Mon, 30 Oct 2017 08:21:04 -0700, tbrowder wrote: > > On Mon, Oct 30, 2017 at 09:53 Elizabeth Mattijsen wrote: > > > > > A —ll-exception stacktrace would be useful in such a case :-) > > > > > > WILCO! $ cat prob.p6 use

[perl #132377] [BUG][POD] tables inside =begin/=end comment pairs cause exception

On Mon, 30 Oct 2017 08:21:04 -0700, tbrowder wrote: > On Mon, Oct 30, 2017 at 09:53 Elizabeth Mattijsen wrote: > > > A —ll-exception stacktrace would be useful in such a case :-) > > > WILCO! Expected "=end comment" to terminate "=begin comment"; found "=end table"

Re: [perl #132377] [BUG][POD] tables inside =begin/=end comment pairs cause exception

On Mon, Oct 30, 2017 at 09:53 Elizabeth Mattijsen wrote: > A —ll-exception stacktrace would be useful in such a case :-) WILCO!

[perl #132195] Feature request: Have Test.pm6 tests accept an optional second description.

On Sun, 01 Oct 2017 18:16:34 -0700, tbrowder wrote: > On Sun, Oct 1, 2017 at 17:23 Zoffix Znet via RT > wrote: > > On Sun, 01 Oct 2017 10:10:55 -0700, tbrowder wrote: > ... > > My vote on this feature is a most definite -1. I see no reason to > > over-engineer a core

Re: [perl #132195] Feature request: Have Test.pm6 tests accept an optional second description.

On Sun, Oct 1, 2017 at 17:23 Zoffix Znet via RT wrote: > On Sun, 01 Oct 2017 10:10:55 -0700, tbrowder wrote: ... > My vote on this feature is a most definite -1. I see no reason to > over-engineer a core module to support some fringe usecase. > The tests routines

[perl #132156] [LTA] Suggest polymod for bases > 36 (9123607.base(37))

On Mon, 25 Sep 2017 02:01:55 -0700, elizabeth wrote: > > > On 25 Sep 2017, at 08:21, Aleks-Daniel Jakimenko-Aleksejev (via RT) > > wrote: > > > > # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev > > # Please include the string: [perl #132156] > > # in the

Re: [perl #129941] [PERF] [IO] Perl 6 text file line read is much slower than Perl 5

On Tue, Sep 12, 2017 at 09:23 jn...@jnthn.net via RT < perl6-bugs-follo...@perl.org> wrote: > On Mon, 24 Oct 2016 03:27:55 -0700, tbrowder wrote: > > On Sat Oct 22 04:24:15 2016, tbrowder wrote: > > > See for a suite > > > of tests that show

Re: [perl #131543] [FEATURE_REQUEST] Add line number method to IO::Handle

On Fri, Jun 9, 2017 at 07:45 Zoffix Znet via RT < perl6-bugs-follo...@perl.org> wrote: > ution to me, ... > but if you really want the `.ln` > method, create a module that mixes it in. IO::CatHandle::AutoLines does > what you want for cat > handles, so you should be able to re-use a lot of its

[perl #127305] EXPORT ignored when unit module/package is used

In a conversation about this issue on IRC channel #perl6 on 25 Oct 2016 starting at approx 06:24, module authors and users express concern about modules polluting the user's namespace. Several main desires IMHO: User: 1. Selective import by object name(s) or tag(s). 2. Selective import by

[perl #128221] [BUG] Weird internal error when parsing some very simple Pod with '-' in the first column of a table in Rakudo

I am working on this issue and would like ownership of it.