| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
also, tests pass again
|
| |
|
|
|
|
|
|
|
|
| |
indices now work from channels, so we have a bunch of workers doing
the parsing, and one worker per index, no lock needed (the implicit
lock in the react/whenever is enough)
next: indices return confidence level, store returns best response
next next: spamc as an index
|
| |
|
|
|
|
|
| |
This reverts commit 314ee051c170c33d2c912b6750f916b73f9cb507.
I think that the bug with LEAVE messes up return values inside
Log::Timeline as well
|
| |
|
|
|
| |
we can `return` from an inner block, even when that block is executed
somewhere else: `return` is lexical!
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
half-tested by hand
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
tried to add some typing, wanted to return `Positional[Str:D]`, but
half the `Array` / `List` methods return `Seq`, empty arrays are
untyped, plus https://github.com/rakudo/rakudo/issues/3383 made the
whole thing a mess
so we're just returning `Iterable`, which is not even parametric, so
we can't promise we're returning strings
|
| | |
|
| | |
|
| |
|
