Commit | Line | Data |
68b6146c |
1 | #!/usr/bin/perl |
2 | |
3 | use strict; |
4 | use warnings; |
5 | |
a28e50e4 |
6 | use Test::More; |
68b6146c |
7 | |
7ff56534 |
8 | |
68b6146c |
9 | =pod |
10 | |
11 | See this for some details: |
12 | |
13 | http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476579 |
14 | |
15 | Here is the basic test case, it segfaults, so I am going |
d03bd989 |
16 | to leave it commented out. Basically it seems that there |
17 | is some bad interaction between the ??{} construct that |
68b6146c |
18 | is used in the "parser" for type definitions and threading |
19 | so probably the fix would involve removing the ??{} usage |
20 | for something else. |
21 | |
d03bd989 |
22 | use threads; |
68b6146c |
23 | |
24 | { |
d03bd989 |
25 | package Foo; |
26 | use Moose; |
27 | has "bar" => (is => 'rw', isa => "Str | Num"); |
68b6146c |
28 | } |
29 | |
d03bd989 |
30 | my $thr = threads->create(sub {}); |
68b6146c |
31 | $thr->join(); |
32 | |
33 | =cut |
34 | |
35 | { |
36 | local $TODO = 'This is just a stub for the test, see the POD'; |
37 | fail('Moose type constraints and threads dont get along'); |
38 | } |
39 | |
a28e50e4 |
40 | done_testing; |