Thanks Brian, I was aware that Types and Slots can be serialised via Streams.
For what I was doing, it was easier and far less overhead to just call toStr() and fromStr() via reflection. So I was just pointing out that Types and Slots, although being annotated with @Serializable { simple = true }, don't actually conform to the Simple Serialisation Specification.
SlimerDude Sat 23 Jan 2016
Hi,
sys::Typeis declared with the following:@Serializable { simple = true } const class Type { ... }The docs for
@Serializable.simplesay:Obviously
Typehas thefind()method which is semantically the same, but should it not also have afromStr()method?I was doing some generic @Serializable handling for simple objects when
Typethrew me this curve ball.Note that
Slotsalso don't have afromStr()method.jay_t55 Sat 23 Jan 2016
.
brian Sat 23 Jan 2016
Types and Slots have built-in serialization which matches their special literal syntax in Fantom:
SlimerDude Sat 23 Jan 2016
Thanks Brian, I was aware that Types and Slots can be serialised via Streams.
For what I was doing, it was easier and far less overhead to just call
toStr()andfromStr()via reflection. So I was just pointing out that Types and Slots, although being annotated with@Serializable { simple = true }, don't actually conform to the Simple Serialisation Specification.brian Sat 6 Feb 2016
Yes that is an over sight, I pushed a fix
brian Mon 8 Feb 2016
Also fixed Field and Method