error256

The only relevant documentation I've been able to find is for [`all-matching-slices`](https://docs.factorcode.org/content/word-all-matching-slices%2Cregexp.html): > Finds a sequence of disjoint substrings which each match the pattern. It chooses this by finding **the...

* ScalaTest does shrinking itself and doesn't care how input is generated, so if, for example, a ScalaCheck generator is used to generate only positive numbers, ScalaTest still can shrink...

> As an effect, if they would be located in an implementation file (i.e. `solution.cpp`), these things will not be possible to be tested. I think it's only a problem...

> ```prolog > test(string_lower_tests, [forall(member(Input-Expect, ["X"-"x", "A"-"a"])), Result = Expect]) :- > string_lower(Input, Result). > ``` `Result` is already unified, so wouldn't `string_lower(_, _).` just pass this?

There's little point to make it in C because there's already a module in C, the tests. The question is whether the code in Preloaded should be assembled separately or...

@DonaldKellett Assuming that [this](https://github.com/codewars/runner/issues/199#issuecomment-1204786974) applies to NASM too: > If the argument is that all C-related boilerplate for assertions can be simply placed directly in the sample / submission tests,...

The thing is that registers often contain not random values, but something relevant in the context, for example, copies of input. I made that fork after my solution that used...

It happens when there are `it` blocks without any assertions in some languages. I've fixed the kata, but I'm not sure if it's considered a runner issue in general or...

As a simpler alternative for now, there's gmpy2 with mutable integers: https://gmpy2.readthedocs.io/en/latest/advmpz.html#the-xmpz-type

`-march=x86-64 -mtune=generic` doesn't really change anything here, I think it's the default. OK, I've solved my original problem with intrinsics with `__attribute__((__target__("avx")))`, so it doesn't matter that much now, but...