Presence of a DESTROY method in base class confuses MX::NM

[ribasushi]

perl -e '
  {
    package GrandParent;

    # this line alone causes MooseX::NonMoose to loose its shit
    sub DESTROY { 1 };

    sub new { bless {}, $_[0] }
  }

  {
    package Parent;

    use Moose;
    use namespace::autoclean;
    use MooseX::NonMoose;

    extends "GrandParent";

    __PACKAGE__->meta->make_immutable;
  }

  {
    package Child;                                                                          

    use Moose;
    use namespace::autoclean;
    use MooseX::NonMoose;

    extends "Parent";

    __PACKAGE__->meta->make_immutable;
  }                                                                          
'

results in

Not inlining a constructor for Child since its parent Parent doesn't contain a constructor named 'new'. If you are certain you don't need to inline your constructor, specify inline_constructor => 0 in your call to Child->meta->make_immutable

[ribasushi]

@haarg this inconsistency may be of interest to you as well

[KES777]

I get similar error. I have App::Schema::Result::Table dumped with dbicdump

Then I change:

-extends 'DBIx::Class::Core';
+extends 'App::Schema::Result';

and add base class. $ cat App/Schema/Result.pm:

package App::Schema::Result;

use Modern::Perl;
use base 'DBIx::Class::Core';

# Put useful things here which will be available from any Result:: class
__PACKAGE__->load_components(qw/
        +HyperMouse::Schema::DefaultResult::HyperMouse
        +HyperMouse::Schema::DefaultResult::I18nRelationships
        +HyperMouse::Schema::DefaultResult::DeepRelationships
        +HyperMouse::MTemporal::Role::Result
        Helper::Row::SelfResultSet
        InflateColumn::DateTime
        EncodedColumn
/);

1;

AFter this I get error for every my Result/Table.pm:

Not inlining a constructor for App::Result::PartnershipObligation since its parent App::Schema::Result doesn't contain a constructor named 'new'. If you are certain you don't need to inline your constructor, specify inline_constructor => 0 in your call to App::Schema::Result::Table->meta->make_immutable

[KES777]

And this error while trying to get data from database:

DBIx::Class::ResultSet::new_result(): App::Schema::Result::PartnershipAgreement->new returned a blessed empty hashref - a strong indicator something is wrong with its inheritance chain at

[Ovid]

For what it's worth, I've a client trying to switch a DBIC hierarchy to Moose. I was getting the returned a blessed empty hashref error. They make heavy use of DBIC components and in one of them, it turns out that it had use Moo at the top of one of the components. Switching that to use Moose made the issue go away.

[jbakerdev]

Is there a recommended approach for the "not inlining a constructor" message?

In my use case (with DBIx::Class and moose-ified Result/Result classes) I have to add:

__PACKAGE__->meta->make_immutable( inline_constructor => 0 );

to all my result classes (which would be the "Child" class in @ribasushi's example