Paul Colomiets

> @elprans @tailhook Paul, we should automatically update the CLI to native m1 build. The hardest part here is not updating CLI to native m1 build but upgrading server to...

> > @elprans @tailhook Paul, we should automatically update the CLI to native m1 build. > > The hardest part here is not updating CLI to native m1 build but...

This should have been fixed.

That sounds like over-engineering: the primary use case for the feature is to quickly past query from the code an fill in the gaps. It's unlikely that there would be...

> Maybe this should be the preferred way of how we implement the feature -- add a compiler flag to accept all arguments as text As I've said in the...

> Yes, but if the query has an $param it becomes unclear how to enter it. The uncertainty goes away if we stick with EdgeQL literals syntax. It's not over-engineering,...

> > No quotes, and immediate feedback means less typos, and means you can test queries from the code right away. > > You can provide immediate feedback and highlight...

> We can have type info about parameter. We first `Parse` the query once normally -- we now have a descriptor for query input. All types are known. We then...

So basically here are three options: 1. Accept EdgeDB literals 2. Accept JSON literals 3. Have custom input for each type Basically (1), (3) both require custom input for every...

> > Native literals, but not default for simple types like numbers and strings > > I still think that strings should require explicit quotes, e.g. > Like I've already...