Pierre-Antoine Champin

> It's already done with the [`prefixes`](https://docs.rs/oxttl/latest/oxttl/turtle/struct.FromReadTurtleReader.html#method.prefixes) method I did look quicly at the oxttl doc (too quickly, obviously!) but I missed it. That's great news. All the more reason...

> Actually I found the `prefixes` method even in RIO: https://github.com/oxigraph/rio/blob/main/turtle/src/turtle.rs#L67 (not sure if it is actually works though) That's why I said I thought it should not be too...

@MajdT51 without a context in your data, and a description of what you are trying to achieve with it, it is hard to understand exactly what you question is...

the two lines `"@nest": "nameType"` is not necessary in your context. As part of a scoped context, those properties (`name` and `testKey`) will only be used on values of `nameType`,...

Agreed, such a big array on the stack may not be ideal. But the fact that it works without lazy_static and fails with it makes it a bug, regardless.

Distro: Ubuntu 23.10 Gnome: 45.1 NB: I'm using wayland, I will eventually try with X.org to check if the problem is also manifesting.

I did some quick test, during which I could not reproduce the bug in X.org, so it *might* be related to Wayland. But this was a very quick test, so...

> That sounds great thanks! My only caveat is the use of the `url` crate where the `iref` crate already handles URLs through the [`Uri` type](https://docs.rs/iref/latest/iref/uri/struct.Uri.html). URLs and URIs are...

> I like the idea, but just to be sure, are we really supposed to create a new `reqwest::Client` for every query? Or recycle the same one? That's a good...

> I can finally, finally, remove all ugly Box and unnecessary trait bounds. That's nice indeed :) > I'm sorry this will make rebasing a bit more difficult. Do I...