Results 82 comments of James Cheney

Interestingly, Kiselyov and Katsushima's APLAS 2018 paper presents a design for incorporating `ORDER BY` and `LIMIT/OFFSET` into comprehension query syntax and uses *effects* to track them. Orderig on fields `l1,...,ln`...

For reference, here is how distinct, grouping and ordering look in [F#'s LINQ syntax](https://docs.microsoft.com/en-us/dotnet/fsharp/language-reference/query-expressions) (based on computation expressions): ``` for e in db.table do ... where (...) yield ... distinct...

I believe @SimonJF is away for a bit. It's totally plausible to me that we might not be doing the right thing here, especially since this may have been tested...

This isn't tremendously surprising, since orderby is supported only by the flat query policy. Since temporal queries are using "query nested" only to benefit from record flattening (i.e. nested records)...

Ah, I had forgotten that bullet point. I'm actually inclined to remove that and keep this issue as a reminder since the other things are either minor or speculative, whereas...

The title of this issue is confusing. I think this is a "question" rather than a "bug". The things to discuss first are: - is it ever actually wrong to...

Huh, I wasn't aware that "client" and "server" could go on var declarations... One could interpret such "located constants" as functions which, when called, yield the constant value. That is...

Of course, what I just wrote completely ignored the fact that `x` is defined as an alien JavaScript thing, that is supposedly placed on the server - that seems nonsensical,...

More generally, for any kind it would be nice to be able to define (parameterized) aliases of things of that kind, uniformly. Something like this syntax: ``` typename Foo(a,b,c)::Kind =...