David Phillips

/test-with-secrets sha=5c2fb2886f53965852b06d5f465b7deef089de5e

Let's use the `{key1 : value1, key2 : value2, ... }` syntax, which matches JSON, JavaScript, Python, Ruby, [Snowflake](https://docs.snowflake.com/en/sql-reference/data-types-semistructured#object-constants), [CQL](https://docs.datastax.com/en/cql-oss/3.1/cql/cql_using/use_map_t.html), etc.

The ambiguity issue seems unlikely in practice, as you wouldn't declare a function with the same name as a type, except in the case where the function is an alias...

We can resolve the ambiguity by allowing it when the function is also a cast (as in the case of `date`), and failing the query otherwise. It looks like `date`...

It is the same as if you wrote it with parentheses: ```sql SELECT (TIMESTAMP '2007-08-09 9:10:11 Europe/Berlin')::VARCHAR; ``` The syntax for type constructors is special because they only support literals,...

Do any of these ambiguities exist if we disallow functions with the same names as types, unless they are equivalent to casts? > The `integer::double` invocation can be interpreted as...

At this point, I think we can simply remove v1.