Runtime support for identity key paths. #18804
Conversation
|
@swift-ci Please test |
|
Build failed |
|
Build failed |
These builtins don't need ownership tracking because they shouldn't ever appear in SIL. NFC
jckarter
force-pushed
the
identity-key-path
branch
from
7e62ffa to
49b6a09
Compare
|
@swift-ci Please test |
|
Build failed |
|
Build failed |
jckarter
force-pushed
the
identity-key-path
branch
from
49b6a09 to
e3c51d6
Compare
|
@swift-ci Please test |
|
Build failed |
|
Build failed |
Make sure the implementation can handle a key path with zero components by removing inappropriate assumptions that the number of components is always non-empty. Identity key paths also need some special behavior: - Appending an identity key path should be an identity operation for the other operand - Identity key paths have a `MemoryLayout.offset(of:)` zero - Identity key paths interop with KVC as key paths to `@"self"` To be able to exercise and test this behavior, add a `Builtin.identityKeyPath()` function and `WritableKeyPath._identity` accessor in lieu of finalized syntax.
jckarter
force-pushed
the
identity-key-path
branch
from
e3c51d6 to
44b55ae
Compare
|
@swift-ci Please test |
|
Build failed |
|
Build failed |
2 participants
Make sure the implementation can handle a key path with zero components by removing inappropriate assumptions that the number of components is always non-empty. Identity key paths also need some special behavior:
MemoryLayout.offset(of:)zero@"self"To be able to exercise and test this behavior, add a
Builtin.identityKeyPath()function andWritableKeyPath._identityaccessor in lieu of finalized syntax.rdar://problem/40538312