Suggestion: How to use some reflection for Registry.cs?

[riemannulus]

Context

The problem with the current Registry.cs is to create a constructor that creates an empty object to deserialize an action.

This is problematic for Actions that use non-nullable fields.

1. Entering an arbitrary value is likely to cause unintended behavior.
2. Changing fields to nullable causes increase code complexity or undefined behavior.

The cause of this behavior is that SysAction reflection is implemented by directly creating an empty object during the instantiation process and putting the value into LoadPlainValue.

libplanet/Libplanet/Action/Sys/Registry.cs

Lines 48 to 49 in 8ff5677

	TypeId.Mint => new Mint(),
	TypeId.Transfer => new Transfer(),

Idea

If we use Activator.CreateInstance, maybe solve this problem.
I wrote some code for a basic idea. (not tested)
https://gist.github.com/riemannulus/7405e0d361364c6afa0ab433905ae81c

Have any opinion on this issue? @libplanet

[riemannulus]

AFAIK, @dahlia wrote this code. Could you have some advice on this suggestion?

[longfin]

• Activator.CreateInstance() had been discouraged due to IL2CPP compatibility. (we may need to investigate furthermore)
• Since system actions has been treated as IAction, there still seems to be code somewhere to initialize it with a parameter-less constructor. thus, it may be a story about IAction (de)serialization, not just Registry.cs.

[riemannulus]

ActionEvaluator 와 TypeLoader 의 리팩토링으로 인해 해당 안은 더 이상 유효하지 않으므로 닫겠습니다.