Limin Fu

Though I am a bit reluctant, I am starting to become inclined to remove async classes. The design and implementation of async classes are quite simple per se, but they...

> @daokoder do you think, that it would be possible to write some highly efficient Dao module providing some form of an actor model (e.g. from the point of view...

> But I prefer not to remove it in hurry, let's give it more consideration, and see if there are ideal use scenarios we have overlooked. Now it is decided,...

> How do the changes related to decorators (i.e. their removal and extension of concrete interface) affect aspect-oriented programming in Dao? Aspect-oriented programming is no longer supported. I think its...

This looks weird. No way should the JIT module be loaded here. Please try a clean build to see if it still happens. Please also try `strace` or (`dtruss` on...

I agree with @Night-walker, we should not divert efforts for this non-essential task. Also, I am not really convinced by Yeppp, when I looked into its repo and try to...

The MurmurHash3 was not only selected for speed but also for simplicity. Since MurmurHash3 is already fast enough and hashing comprises only a tiny fraction of the total execution time...

> For small buffers or usage in a hash table FNV1 is still the fastest. Due to its simplicity, it should be quite fast. Just curious, are there many FNV...

> as it's significantly faster and with a state of the art distribution of keys. Where did you see this? Please note speed is not the most important factor in...

> This is interesting. Are there any places in Dao which require that? Or do we expose it somewhere, so that it allows e.g. sending a computed hash over network...