\u65e7iOS\u9879\u76ee\u6253\u5f00\u62a5\u9519\uff1a’Expression’ is ambiguous for type lookup in this context<\/p>\n\n\n\n
import<\/strong> SQLite<\/p>\n\n\n\n filter: Expression<Bool>? = nil<\/strong>, select: [Expressible] =\u00a0<\/p>\n\n\n\n <\/p>\n\n\n\n \u539f\u56e0\uff1a<\/p>\n\n\n\n The iOS 18\/macOS 15 SDK now includes a new type called\u00a0 \u5904\u7406\uff1a<\/p>\n\n\n\n This causes a name conflict with the\u00a0 filter: Expression<\/code><\/a>\u00a0in\u00a0Foundation<\/code>. This seems to just be a version of\u00a0Predicate<\/code><\/a>, except it can output any type, not just\u00a0Bool<\/code>.<\/p>\n\n\n\nExpression<\/code>\u00a0type declared in\u00a0SQLite<\/code>. You need to write\u00a0SQLite.Expression<\/code>\u00a0to clarify. Or you can declare a type alias:<\/p>\n\n\n\ntypealias SQLExpression = SQLite.Expression<\/code><\/pre>\n\n\n\nSQLite<\/code>.Expression<Bool>? = nil<\/strong>, select: [Expressible] =<\/p>\n","protected":false},"excerpt":{"rendered":"