Sönke Ludwig

In this case, I'd refer to [RFC1738](https://datatracker.ietf.org/doc/html/rfc1738). For schemas that do not fall in that category, something like this would be valid, though: `foo:bar`.

Yeah, but the one you mentioned would be what I'd associate with `parseFuzzyURL` (or whatever it would be called).

> But RFC1738 is obsolete (although there's probably a lot of overlap)... The RFC tracker doesn't make this very obvious, but AFAIK the "proper" RFC for would be RFC 3986....

We'll have to go through a deprecation phase here to avoid the immediate breakage. I'd suggest to add two new definitions (`uuidOld = 0x03` and `uuidNew = 0x04`) and then...

I agree that we should go this route. `shared static this` was basically just a marketing feature in the early days to be conpetitive with scripting languages in terms of...

This isn't even just a bad error message since something like `{"baz": 0, "bar": 0, "test": "..."}` would fail as well, while it should actually pass. What's missing is a...

Currently it's a boolean choice - by default only one thread with an infinite number of fibers is used. If `enableWorkerThreads` is called (this function will be removed eventually) then...

Since 0.7.17 there is also [TaskLocal!T](http://vibed.org/api/vibe.core.core/TaskLocal), which is recommended now (the old `Variant` based get/set methods will get deprecated eventually as they are slower and don't support static type checking)....

Async I/O (i.e. anything that yields execution or needs the event loop) - Basically `TaskMutex` works exactly like `Mutex`, but does not block the event loop when it needs to...

No, they always stay on the thread where they have been started. They have to, so that they don't violate D's threading model (i.e. un-`shared` references would be shared across...