sorear: looks even C is bad for static analysis - the biggest problem coverity have was differences in flavours of C in used compilers. and it is why I bring that link here, to language-still-under-development forum... maybe something can be changed before many Perl6 dialects appear

moritz: just see that C looks like small and simple language and so many problems. and Coverity had a lot of human-lvl problems, eg.: use-after-free found - answer: "So ? It will crash. We will get a call." :)

std dc62e1d: OUTPUTÂ«[31m===[0mSORRY![31m===[0mâ�¤Variable $.a used where no 'self' is available at /tmp/_odt_h6ucV line 1:â�¤------> [32mclass A { has $.a; has $.b; has $.c = [33mâ��[31m$.a + $.b }[0mâ�¤Variable $.b used where no 'self' is available at /tmp/_odt_h6ucV line 1:â�¤------> [â€¦

std dc62e1d: OUTPUTÂ«[31m===[0mSORRY![31m===[0mâ�¤Variable $!a used where no 'self' is available at /tmp/jxNvCkt_ju line 1:â�¤------> [32mclass A { has $.a; has $.b; has $.c = [33mâ��[31m$!a + $!b }[0mâ�¤Variable $!b used where no 'self' is available at /tmp/jxNvCkt_ju line 1:â�¤------> [â€¦

phenny: tell moritz I changed Numeric to a role. It was trouble-free. I did similar with Real, and it fails various tests. If you fancy having a look, see the real-trouble branch; feel free to toss it back to me if you don't have a good idea of a fix.

..niecza v13-246-g1ae3990: OUTPUTÂ«[31m===[0mSORRY![31m===[0mâ�¤â�¤Lexical symbol '&infix:<+>' is already bound to an outer symbol (see ??? line 0);â�¤ the implicit outer binding at line 1 must be rewritten as &infix:<+>â�¤ before you can unambiguously declare a new '&infix:<+>' in this scopâ€¦

..niecza v13-246-g1ae3990: OUTPUTÂ«[31m===[0mSORRY![31m===[0mâ�¤â�¤Lexical symbol '&infix:<+>' is already bound to an outer symbol (see ??? line 0);â�¤ the implicit outer binding at line 1 must be rewritten as &infix:<+>â�¤ before you can unambiguously declare a new '&infix:<+>' in this scopâ€¦

rakudo/nom: Use the constant folder on enum values. Note that the hack in Perl6::World means this code is *only* safe for use in this particular case for now (the folder is general, the code in World is not).

it can *read* Mach-O fine, generation is what fails (which is why no binutils but only Apple's tools). but debugging is weird, in particular if you try to step through (including the implicit stepping done when you just want function entry/exit) and it tries to call into a dylib, it gets lost

linux started out way back in the beginning with the idea of maybe shuffling stuff up to catch people being nonportable, then discovered that all that accomplished was to make sure nobody ported anything...