Jeremy Schonfeld

Yeah we can keep this issue to track investigating supporting the concept of "now" within the evaluation of the predicate. I think we'll likely want to represent this as `Date.now`...

> This message is a bit misleading as a predicate with a keypath like \Dummy.sub.optionalString, where only optionalString is optional, can be created without issue. I think this behavior that...

Those two are currently unavailable because the APIs that they represent (`String.localizedStandardContains` and `String.localizedStandardCompare`) are not yet available in the package. We can add the `Predicate` operators as soon as...

You're definitely on the right track! Two things from your sample code to take a look at: 1. On [Line 65](https://github.com/ordo-one/external-reproducers/blob/a0ef474b9afcd587b1e6e4a1acd5b7a4497d2e0a/swift/predicate-optional-keypath2/Sources/PredicateKeyPathProviding.swift#L65): The type of the parameter `ofType` is `LeafType`, but...

In your case, this is a scenario where you're trying to unwrap an existential and pass it to a generic function. [SE-0352](https://github.com/apple/swift-evolution/blob/main/proposals/0352-implicit-open-existentials.md#explicitly-opening-existentials) lifted some restrictions here and current allows doing...

@axelandersson thanks for bringing this up! That's definitely interesting. It appears that the stdlib has a special overload to allow `==` comparisons between an `Optional` wrapping some non-`Equatable` and a...

> @jmschonfeld @parkera - I don't understand this failure unfortunately. Locally I am not seeing this precondition failure. It looks like the precondition failure is happening because `SHGetFolderPath` is returning...

I believe we added the `Decimal` conversion a little while back to support formatting values between `Int64.max` and `UInt64.max` so that numbers like `UInt.max` (equivalent to `UInt64.max` on some machines)...

Thanks for bringing this up! This is a limitation of `Predicate`s currently. `Predicate` uses `KeyPath`s to reference properties, but as it stands today Swift does not support `KeyPath`s for static...

Yeah, I think I'd agree with you that adding `is...Equal()` functions for all of the possible combinations we support might be a bit drastic given `StringProtocol` is pretty highly used/fundamental....