This PR chases down some simplifications due to the removal of abomonation, looking forward to flexibility enabled by containers.
Specifically, the Message<T> type has wrapped several ways to present a T, including owned and borrowed forms, as well as numerous accessors. All of the borrowed forms have been dead code since the abomonation removal, and the attendant complexity unwarranted. This PR removes it.
Going forward, distinctions between owned and borrowed seem best housed in containers, which can themselves resemble MessageContents<T> which was the enum that could be owned or borrowed. The Message<T> type remains, but seemingly only to support serialization methods, but this behavior could be move into a trait that containers are expected to implement if they are to be used for exchange edges.
This PR chases down some simplifications due to the removal of
abomonation, looking forward to flexibility enabled by containers.Specifically, the
Message<T>type has wrapped several ways to present aT, including owned and borrowed forms, as well as numerous accessors. All of the borrowed forms have been dead code since theabomonationremoval, and the attendant complexity unwarranted. This PR removes it.Going forward, distinctions between owned and borrowed seem best housed in containers, which can themselves resemble
MessageContents<T>which was the enum that could be owned or borrowed. TheMessage<T>type remains, but seemingly only to support serialization methods, but this behavior could be move into a trait that containers are expected to implement if they are to be used for exchange edges.