Nick Smith

Actually, I suppose even the use of literals in types can trigger side-effects, because passing a literal as a parameter often implies a conversion to another type: ``` struct Foo[x:...

As @soraros pointed out, this syntax extends naturally to result parameters. I added a section to the end of my original post demonstrating this. Serendipitously, it turns out that this...

Given the following function signature: `fn foo(x: SomeType, y: SomeType) -> [T: SomeTrait](result: T):` I'd imagine the syntax for assigning outputs to variables would look something like this: `alias Type:...

@Mogball mentioned on the community call that syntax issues with this NRVO proposal are being worked through right now, so this seems like a good time for me to bring...

@lattner Our point is that these issues are intertwined, because NRVO and tuples are fighting for the same position in the grammar. Only one syntax can win 😎. (But I'll...

> the "Type as name" syntax was chose to align with python pattern syntax. If you're referring to the pattern syntax `case Point() as p:`, then the syntax you've chosen...

Anyway I'm glad to see this feature land. 🥳 This is a really clean way to eliminate unnecessary moves, and to initialize non-movable types.

It's probably not a surprise, but my personal opinion is that Mojo's syntax for tuple types should be consistent with Python, because there aren't really any reasons to diverge. Certainly,...

Mojo doesn't really have the freedom to coin a new name for an established Python concept. I suspect the only option here is to look at the facts—i.e. what is...

A change was made between A-Frame version 0.6.1 and 0.7.0 that has caused this behaviour. Until this is fixed on the A-Frame side (if it ever is), users of this...