Could the ambiguous unflatten() issue be solved by adding type hints?

[pnck]

There have been some relevant issues:
#1575
#1989
#2123

But it seems nobody suggested introducing some typing annotations or hints, like this:

{"0":"v0","1":"v1"} // flatten() => {"@O/0": "v0", "@O/1": "v1" }
["v0",v1"] // flatten() => {"@A/0": "v0", "@A/1": "v1" }

Or separate the type info to another item:

{"obj":{"0":1, "1":2}, "list":[1,2]} // flatten() => {"/obj": "@object",  "/obj/0": 1, "/obj/1": 2, "/list":"@array", "/list/0": 1, "/list/1": 2}

Or a new child item:

{"obj": {"0": 1} } // flatten() => {"/obj/@object": null , "/obj/0": 1}

What do you guys think of this?