Adrián Arroyo Calle

Yeah, it's true. Sometimes I wanted to be extra sure :), I'll try to fix them later

Thanks for the suggestions. I've never used so many DCGs before, and in this "contest" I'm learning a lot about them (in fact, quite embarrassing, sometimes I've spent more time...

@Mousaka I don't have any problem discussing solutions here hahaha, beware that I do not consider myself a Prolog expert (I'm reading @triska post with lots of interest right now...

Today's solution (day 15) is not going to like @triska because it is non-pure and non-portable, but it is the fastest way to get a result (and avoid stack limits)...

Really nice!! I need to do more Prolog still to come up with those elegant solutions. I've seen on Reddit that some people used a [Trie](https://www.swi-prolog.org/pldoc/man?section=trie) and achieved results under...

Ups, I forgot to told you that I've already tried that but on SWI (which is what I'm using right now, but I'll port it to Scryer once finished the...

This puzzle is very easy to solve, but not so easy to understand why (at least on my mind). The thing is that at every transformer in a solution, you...

I do not think that having a u64 for inferences is reasonable, at least if we want Scryer to be stable long time running (I don't know what are BLIPS...

@UWN in #1083 it was said that a separate predicate would be an option. These predicates only apply to TcpStream (reading now, maybe it's not clear from the original text).

That would work too but I'm not sure it's worth duplicating every read/write predicate. Implementation will also be more complicated