So far it is specially designed for ObjectRef types, so that we can use nullptr to store the not an option.
The advantage is that the `Optional<T>` is essentially `T` during runtime and won't incur additional storage cost. It is more like a better typing protection in the C++ rather than creating a new wrapper that has an additional nullopt field. Due to the restrictions of only working with the ObjectRef, it is not compatible with the `std::optional`, which might need to introduce additional storage to support any types --- [Visit Topic](https://discuss.tvm.ai/t/allow-non-nullable-object-and-introduce-optional-t/6337/8) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/368c05c7982f245df848855869af7489bdec5b098891f974003a8a88ced48a8b).
