RequestSerialization is technically a
built-in, but there's no reason to
prevent extension by developers
(or warn against it, depending on
the IDE).
An example of this usecase is
the common pattern of calling RequestSerialization() and then
OnDeserialization(). By extending
RequestSerialization we can declare
that we always will call
OnDeserialization afterwards, reducing
boilerplate.
Other examples: if we would like
to update an atomic clock by one
whenever we call RequestSerialization,
or we might want to automate assigning
ownership.
RequestSerialization is technically a built-in, but there's no reason to prevent extension by developers (or warn against it, depending on the IDE).
An example of this usecase is the common pattern of calling
RequestSerialization()
and thenOnDeserialization()
. By extendingRequestSerialization
we can declare that we always will callOnDeserialization
afterwards, reducing boilerplate.Other examples: if we would like to update an atomic clock by one whenever we call RequestSerialization, or we might want to automate assigning ownership.