[Feature] messages.next() returns a different address object

[javeme]

          > always return the same Object is reduce memory pressure and avoid GC

Yep~ But semantically, messages.next() returns a different address object more intuitive.
Otherwise, someone who call this function downstream need to clearly know that the same object is returned here, which is not logically intuitive and easy to make mistakes.

Do we have some more elegant solutions?

Originally posted by @diaohancai in #275 (comment)

[diaohancai]

We hope that after the memory management module is added, this confusion can be solved.

Great~ Could you disclose the design for the memory management?