Kauê Hunnicutt Bazilli
Kauê Hunnicutt Bazilli
> So far, I believed that resorting to Prolog terms would be the best representation, but another option might be to use [Modified UTF-8](https://en.wikipedia.org/wiki/UTF-8#Modified_UTF-8) which assigns some two-byte encoding to...
> There is no such space. That is it would produce garbage all the time I don't understand, could you elaborate? Can't we encode it like I showed?
Ok, that makes complete sense, thanks for the explanation. I still wonder if there is a way to avoid sentinels without space concerns, but with this I'm convinced that inlining...
I just thought about an optimization: if we have an inlined partial string that contains zero bytes, we don't need two allocations, we can reuse that zero byte as a...
> How does this scheme avoid the creation of any auxiliary datastructure? It avoids an indirection and the need for a `PartialStringLocation` cell. ``` Indirection: Cell 0: ListPointer(1) % Here...
Added a task list for this.
Doing this in the current Scryer site will be kind of hard because, if I understand correctly, Doclog would need some extra features to be able to document predicates not...
An idea I just had that is better than linking to SWI is just documenting these predicates inline in the module documentation. This has the added benefit that you don't...
> Although I haven't done it yet, my idea was to support the parsing of extra files. Yes, this would be the obvious solution. But this opens a lot of...
The problem is in line 18: ``` #offset_coords : bagof(X-Y,offset_coord(X-Y),Bag),Bag. ``` I don't actually know what you meant here, but I guess the `:` is a mistyped `:-`, and the...