RFC: Protected value representation about rescript-compiler

[cometkim]

I will experiment with a new @deriving attr in a branch

[cometkim]

I ran a few more thought experiments, and here is the counter I found:

Symbols are not sent out of bounds without explicit serialization. This potentially creates many problems in web environments with different context boundaries.

For example, React RSC is sent from another boundary. React elements are included in the serialization because it is their knowledge, but there is no way to include ReScript-specific knowledge in the serialization. It all happens implicitly (unfortunately). As a result, any deriving comparison of it with values outside the boundary will fail and fallback to deep-equal.

[cometkim]

Closing this, @deriving(shallowEquals) for each record would be better for rescript-lang/rescript-react#111

[cometkim]

I think we still need a way to determine which values are ReScript values, but we can't do that before a standardized serialization method.