Hi @findepi

Would like to give this shot.
Does the implementation require anything other than adding the operator to grammar, and handling the change in AstBuilder? (other than tests and documentation).

@vVv-AA implementation-wise I think it's exactly as you said, but @martint may know better.

The SQL spec reserves double colon for static method invocations, so that's incompatible with this proposed cast syntax.

<static method invocation> ::= <path-resolved user-defined type name> <double colon> <method name> [ <SQL argument list> ]

For example, given: foo::bar, it could be interpreted as:

• Cast the value of column foo to type bar
• Invoke method bar on type `foo.

@martint If I understood correctly, this would make the grammar ambiguous?

Since many dbs are not following the spec and having :: do casting instead, would it somehow be possible to let the behavior somehow be pushed down to DBs so their can handle it as per their own implementations?

The shorthand ::, ?:: for cast and try_cast helps a lot with readability, but if :: does not work, would it be okay to have some custom one in trino, say :::, ?::: for lack of creativity on my part?