Klemens Böswirth

> It could be misuse because no other namespace was available. If you define "cascading" as "only for lookup" then it clearly is. > Or it simply unveils bugs/misuses. Unlikely....

> Can we then agree on ksSearch behaving like ksLookup? Yes, if there will be a separate namespace e.g. `data:/` then doing a lookup in `ksSearch` is fine.

Please rebase and complete this PR, or close it if you don't intend to finish it.

Please fix the formatting issues, so the build server can run all jobs.

There is now another formatting issue. Please fix this one too.

Please fix the formatting issues and try to get the CI to run. It would be shame, if all the work in this PR went to waste.

Probably best if we check all tutorials/docs and mark everything outdated with e.g. `[Deprecated]` in the title (since I doubt we have time to update everything).

> For 1.0 we should either update or remove. Of course, but... > Before 1.0 it is enough to have issues that say that something is outdated/missing. ... since people...

Could you please try again... The error basically means that Gradle couldn't find the dependency `com.thoughtworks.xstream` (which is required by the `gradle-versions` plugin, we use). As far as I can...

Honestly, I'm not sure how this example ever could've worked. It doesn't call `kdbSet` at any point and doesn't insert a key into `ks`, yet the example expects `ks.lookup(key)` to...