Michael Toy

does this break in the world of `extend: {` instead of `declare:`

If we did something like this, it would probably be ``` sql: { ddl: SQL_STRING connection: ... } ``` No "name" would be allowed and you wouldn't use `select:` ......

this is done, right?

I'd be happier if we made ``` dimension: x is x+1 ``` work, and then this would be `dimension: startYear is startYear::number`

close this?

So the problem is the name space active for expressions is the output space ... layered on top of the input space, so while this is technically not a circular...

Chris is correct, malloy has two cast gestures ... `::` and `cast` and `::` generates a safe cast on bigquery. I think the change which should go in immediately is...

I think the way it is now is that `::` is cast and `:::` is safe cast, for all dialects. I'll let @christopherswenson comment, but I think we should close...

Malloy doesn't grok the "TIMESTAMP WITH TIME ZONE" type, with the timezone work, that will get fixed. Casting it to timestamp will let you use it in Malloy for now....

hmm ... i think maybe we didn't check for >= or