Codable != Archivable

Rod_Brown · January 31, 2019, 2:44am

My apologies, you’re correct it doesn’t inherit from NSObject, though I think your comments about runtime depend on the platform and other marks as noted in the code below

I did prefix my words with “I believe” because I wasn’t sure, I remembered reading about SwiftObject and got confused by the NSObjectProtocol conformance vs inheritance from the class. Admittedly, it was also years ago.

For reference, the real stuff is here:

github.com

apple/swift/blob/main/stdlib/public/runtime/SwiftObject.h

//===--- SwiftObject.h - Native Swift Object root class ---------*- C++ -*-===//
//
// This source file is part of the Swift.org open source project
//
// Copyright (c) 2014 - 2017 Apple Inc. and the Swift project authors
// Licensed under Apache License v2.0 with Runtime Library Exception
//
// See https://swift.org/LICENSE.txt for license information
// See https://swift.org/CONTRIBUTORS.txt for the list of Swift project authors
//
//===----------------------------------------------------------------------===//
//
// This implements the Objective-C root class that provides basic `id`-
// compatibility and `NSObject` protocol conformance for pure Swift classes.
//
//===----------------------------------------------------------------------===//

#ifndef SWIFT_RUNTIME_SWIFTOBJECT_H
#define SWIFT_RUNTIME_SWIFTOBJECT_H

This file has been truncated. show original

Nevertheless the point stands that switching base class is under a devs control, with no real downside and not something to eschew for any specific reason.

Edit - also another thread about the Obj-C base class. I assume this means that it at least participated in the Obj-C runtime on all Darwin-based platforms?