Arnaud Golfouse

I am wondering if `addr` could be a _list_ of addresses: then a reborrow would append to that list, meaning that - A borrow and its reborrow are 'compatible', since...

Hm, I see...

I added a third field, that is *not* inherited for reborrows currently (a new one is generated for each borrow/reborrow). This is equivalent with the previous approach, while fixing the...

So we talked about this, and here is what we think should be done: - Borrows should have a third "addr" (or "id") field (this is the current state of...

To disallow the use of comparisons (`==`, `!=`) inside `gh! { ... }` blocks

> Is this related to #391? Note the comment with the minimized grammar [#391 (comment)](https://github.com/lalrpop/lalrpop/issues/391#issuecomment-778940697) They look similar, but there is in fact a key difference. In summary, I believe...

The more I look at it, the more I wonder if the macro `enum_operation` is truly necessary. Could we not just use `DijkstraMap::apply_operation` everywhere ? Maybe then you'll say that...

Btw, there are some clippy-related warnings still fired by the crate in this state.

As we discussed, I put an alternative design here : https://github.com/arnaudgolfouse/Dijkstra_map_for_Godot/tree/alternative-operation-design Feel free to take whatever interests you !

I believe the rust bindings for Godot 4 are not quite ready yet (at least last time I checked): see https://github.com/godot-rust/gdext. I think @astrale-sharp is already working on it, but...