A declaration cannot be both 'final' and 'dynamic' error in Swift 1.2

后端 未结 7 1351
Happy的楠姐
Happy的楠姐 2021-01-30 07:55

The declaration of value below

import Foundation

class AAA: NSObject {
    func test2() {
        self.dynamicType
    }
}
extension AAA {
    stat         


        
相关标签:
7条回答
  • 2021-01-30 08:17

    I solved this issue by moving the static declaration into the new struct I defined in the extension.

    So instead of this:

    extension NSOperationQueue {
        static var parsingQueue : NSOperationQueue = {
            let queue = NSOperationQueue()
            queue.maxConcurrentOperationCount = 1
            return queue
            }()
    }
    

    I have this:

    extension NSOperationQueue {        
        struct Shared {
            static var parsingQueue : NSOperationQueue = {
                let queue = NSOperationQueue()
                queue.maxConcurrentOperationCount = 1
                return queue                
                }()
        }
    }
    
    0 讨论(0)
  • 2021-01-30 08:17

    You can mark it as private to prevent this error. If you want to expose it, you can wrap it in a public function:

    extension AAA {
    
        private static let value = 111
    
        public func getDatValue() -> Int {
            return AAA.value
        }    
    }
    

    In my case, I only referenced the property in the extension itself, so there was no need to expose it.

    0 讨论(0)
  • 2021-01-30 08:24

    You will get this error if your class satisfies these conditions.

    • Subclassed from NSObject.
    • Has a static let field.
    • Accesses the field from an instance method via dynamicType.

    I don't know why this happens, but you can try this workaround.

    static var value: Int {
        get {
            return 111
        }
    }
    

    Or in shorter form.

    static var value: Int {
        return 111
    }
    

    Use static var { get } instead of static let.


    Though property getter and its calling cost is very likely to be eliminated by LLVM optimiser in above example, you might want to avoid it explicitly.

    If you're concerned about such value calculation cost, you can create it once and cache like this.

    static var value: Int {
        return cache
    }
    private let cache = getTheNumber()
    

    Or like this if you want to hide the existence of cache completely.

    static var value: Int {
        struct Local {
            static let cache = getTheNumber()
        }
        return Local.cache
    }
    
    0 讨论(0)
  • 2021-01-30 08:28

    As a slight improvement over @Eonil's answer, the get not necessary:

    static var value: Int { return  111 }
    
    0 讨论(0)
  • 2021-01-30 08:31

    This issue arises because Swift is trying to generate a dynamic accessor for the static property for Obj-C compatibility, since the class inherits from NSObject.

    If your project is in Swift only, rather than using a var accessor you can avoid the issue via the @nonobjc attribute in Swift 2.0:

    import Foundation
    
    class AAA: NSObject {}
    extension AAA {
        @nonobjc static let value = 111
    }
    
    0 讨论(0)
  • 2021-01-30 08:31

    I had this error too.

    My issue was just a static var in a swift extension.

    extension NotificationsViewController: UITableViewDataSource , UITableViewDelegate {
    
        static var timeIntervalFormatter = NSDateComponentsFormatter()
    
    }
    

    Moving it to the class implementation resolved the problem for me.

    0 讨论(0)
提交回复
热议问题