It looks like this coder/decoder was introduced in imitation of some other types, but the other types that have erroring implementations either:
Do not exist on any instance (Region3)
Are special-cased elsewhere downstream (Ref)
Wouldn't work anyway? (SharedString, although I think there is a case to be made that SharedString should NOT have an erroring lua coder/decoder)
SecurityCapabilities exists on all instances so an erroring implementation is inappropriate and causes problems for Rojo as per rojo-rbx/rojo#802. I think we can just remove the lua encoder/decoder, like how UniqueId simply doesn't have them either.
It looks like this coder/decoder was introduced in imitation of some other types, but the other types that have erroring implementations either:
Region3)Ref)SharedString, although I think there is a case to be made thatSharedStringshould NOT have an erroring lua coder/decoder)SecurityCapabilitiesexists on all instances so an erroring implementation is inappropriate and causes problems for Rojo as per rojo-rbx/rojo#802. I think we can just remove the lua encoder/decoder, like howUniqueIdsimply doesn't have them either.