From @carbin

If you have a file, Boom.pm6, that contains​:

  class Boom;

  Boom.^add_fallback(-> $, $ { True },
  method ($name) { }
  );

And another file, First.pm6, that `use`s that module​:

  use Boom;

  class First { }

And finally, a file that uses First.pm6​:

  use First;

  class Second { }

And then precompile these files, in dependency order (Boom.pm6 ->
First.pm6 -> Second.pm6), compiling Second.pm6 fails with​:

===SORRY!===
STable conflict detected during deserialization.
(Probable attempt to load two modules that cannot be loaded together).

A real world example of this is Inline​::Perl5; this bug makes it
impossible to precompile any module that `use`s a module that `use`s
Inline​::Perl5.

--
Carlin

From @jnthn

On Tue Sep 16 13​:58​:54 2014, carlin wrote​:

If you have a file, Boom.pm6, that contains​:

class Boom;

Boom\.^add\_fallback\(\-> $, $ \{ True \},
    method \($name\) \{ \}
\);

This should be done in a BEGIN block, so the effects are pre-compiled. Doing the modification on every module load will quickly lead to two competing versions of the same modification being serialized, and...

===SORRY!===
STable conflict detected during deserialization.
(Probable attempt to load two modules that cannot be loaded together).

...that is exactly what happens. While the error might use some work to explain it better, it happens when a type is modified and then serialized in two different ways. That was never the intent here, and the BEGIN should take care of it nicely.

/jnthn

The RT System itself - Status changed from 'new' to 'open'