Vadim Belman

There must be a way to manually specify which address to use, no matter what type of address it is and wether it is source or destination. Consider a corporate...

This would be a headache if a big system would require different binding for different connections. Why can't we have a unified address kind of type? Say, similar to perl5,...

With regard to the expected behavior, `!` is a meta. Basically, it is a shortcut for `!()`. In this particular case, to `!($a == $b)`. So, two rules: - one...

@2colours I barely can add much to the discussion in rakudo/rakudo#3874. Neither I have much spare time for this kind of discussions these days. Just two notes. How many questions...

Augmentation was already discussed a while ago, though I can't neither recall nor find the exact issue where it took place. But the conclusion I carried out of it is...

As to my view there are only two possible solutions: 1. Remove the specs for Perl5 embedding from roast 2. Incorporate `Inline::Perl5` into Rakudo

I'm equally ok with both ways. The 1 could be done in a way of reducing tests to the basic ability of using `:lang`.

> Come to think of it: such a mechanism generalized could make spectest a more general tool? Maybe a "make integrationtest" that would run all the test-suites of any installed...

@niner thanks for the detailed explanation! But it actually underlines the whole point of this issue. With special measures taken we would rather discuss the test which doesn't conform to...

I forgot to mention that due to changes logic of the latest macOS versions environment-variable based loading of dynamic libraries doesn't work anymore. In my case the problem was triggered...