Maybe more a question than an issue:
Some constants in Keychain.swift show as deprecated in watchOS 7.0 (see screenshot). But some of those are just used inside a constant with @available(watchOS, unavailable). Why does this give a warning? Can't the compiler infer that the deprecated constants are only used inside unavailable code? Is this a flaw in LVVM? Can we somehow make these warnings disappear?
Maybe more a question than an issue: Some constants in
Keychain.swift
show as deprecated in watchOS 7.0 (see screenshot). But some of those are just used inside a constant with@available(watchOS, unavailable)
. Why does this give a warning? Can't the compiler infer that the deprecated constants are only used inside unavailable code? Is this a flaw in LVVM? Can we somehow make these warnings disappear?: