Late request for talk proposals for FOSDEM 2018 - 4 talks needed

2018-01-01 Thread Wendy
Dear Perl Mongers, We have just been told by FOSDEM orga that we need to fill in our schedule now. I really have been too lazy to start asking for more talks this late. In case you're reading this, and really want to come to FOSDEM to talk about Perl in the Perl-devroom, a good talk

[perl #132673] [JVM] Container has no information about parametric type

2018-01-01 Thread via RT
# New Ticket Created by Christian Bartolomaeus # Please include the string: [perl #132673] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132673 > After a recent change to roast [1] there are some new failing tests on the JVM

[perl #128287] [BUG] Type check `Array[Foo]` in module gets confused if `Array[Foo]` was already referenced in another precompiled module.

2018-01-01 Thread git...@zwell.net via RT
On Sun, 29 May 2016 10:28:43 -0700, sml...@gmail.com wrote: > It's as if we end up with two "instances" of the same parameterized > type, and the type check gets confused about which one to check > against. If I'm understanding the code correctly, it looks like that's what's happening. The error

[perl #128287] [BUG] Type check `Array[Foo]` in module gets confused if `Array[Foo]` was already referenced in another precompiled module.

2018-01-01 Thread git...@zwell.net via RT
Also, if you print the .WHICH values during BEGIN, you'll find that they're consistent, so the problem occurs either when compiling A.pm or reading the precompiled data.