John Wostenberg

I've been playing around with this in a fork - I've gotten For, Select, and Join to work by just always using a table alias based on the variable names...

> What would the syntax look like? No syntax nor SqlHydra API surface changes - my fork is just automatically aliasing everything based off the variable names already used. So...

> Using the `foo` and `bar` instance names for the alias is _really cool_. My only concern is that it adds a fair amount of complexity to the code. Given...

> Go ahead and submit this as a PR and I will test it and get it merged. Sweet, doing a draft PR. Still working on it; there's a lot...

Yeah, it's definitely a wide-reaching thing -- I think it's very much worth it. Just FYI it's still very much a half-baked PR so far; so you'll probably find a...

@charlesroddie that's true, but there could be value in providing the suggested (or similar) syntactic sugar. If it would get used enough, I think it could be a valuable shorthand....

Continuing on my last comment, these shorthand properties could instead take the associated arguments as parameters, to handle things like nested tuples nicely, at the expense of slightly cluttering simpler...

Come to think of it, `fixed` should probably also support `Memory

I say we should also support arbitrary pinning of refs. For example, C# lets you do the following (shamelessly copied from [the C# docs](https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/fixed-statement)): ``` class Point { public int...

@dsyme what do you think about supporting GetPinnableReference vs supporting any `ref`? Would an RFC be approved if it contained both?