Chris Lattner Comments - Answer Overflow

well you're doing great work! FYI, one of the things we're working on is to make it so the max graph api propagates shapes implicitly as part of graph building, even when they are parametric. This will get rid of the unknown dimensions, and elimiante the need for "shape op" operators etc. I think this can also allow a pretty nice UX because we can report shape errors at graph build time instead of at graph execution time.

47 replies

MModular

•Created by TilliFe on 7/18/2024 in #community-showcase

Endia

TilliFe, custom ops are 🔥. I'm loving your work here. What is your background working with JAX?

47 replies

MModular

•Created by TilliFe on 7/18/2024 in #community-showcase

Endia

This is amazing work @TilliFe !

47 replies

MModular

•Created by ivellapillil on 5/15/2024 in #community-showcase

Online book on Mojo

This is amazing work @ivellapillil , incredible!

34 replies

MModular

•Created by toasty on 3/7/2024 in #questions

Disambiguation of a call to an overloaded function when the argument satisfies multiple signatures?

It'd be great to give this approach a try - if the compiler doesn't consider it to be more-specific then please file a bug 🙂

8 replies

MModular

•Created by toasty on 3/7/2024 in #questions

Disambiguation of a call to an overloaded function when the argument satisfies multiple signatures?

Interesting use-case. One way to address it is to implement another overload that requires W to be both Writer AND StringWriter. This should be (but I'm not sure if the compiler does this yet) considered more-specific than either of the other conversions, so it should resolve the ambiguity

8 replies

MModular

•Created by vmois on 12/30/2023 in #questions

Owned convention does not destroy variable after transferring ownership

There are a few bugs in this area, and hte model got a bit simplified (e.g. take semantics is removed from the ^) operator. The next update will be a big one in this department

5 replies

MModular

•Created by NickJJ on 12/30/2023 in #questions

Adding __takeinit__ makes a difference in assignment

this does refine/clarify/narrow that x^ does though!

22 replies

MModular

•Created by NickJJ on 12/30/2023 in #questions

Adding __takeinit__ makes a difference in assignment

x^ is still allowed and is used when you want to end the lifetime of a value. This is an exotic thing that system programmers may care about (e.g. with move only or non-movable types) not something that app-level programmers will care about.

22 replies

MModular

•Created by gryznar on 1/3/2024 in #questions

Safe pointers

I expect significant progress on both fronts by the end of Q1

6 replies

MModular

•Created by gryznar on 1/3/2024 in #questions

Safe pointers

2) dangling pointers. This is currently a major footgun, and will be fixed by the "lifetimes" feature once complete and pushed through the standard library

6 replies

MModular

•Created by gryznar on 1/3/2024 in #questions

Safe pointers

1) array bound checking, e.g. when subscripting into an array type. These will definitely need to be checked (at least for the standard types like array), but there will also be more exotic unchecked things.

6 replies

MModular

•Created by gryznar on 1/3/2024 in #questions

Safe pointers

hi gryznar, there are two subproblems here:

6 replies

MModular

•Created by NickJJ on 12/30/2023 in #questions

Adding __takeinit__ makes a difference in assignment

Cool, it really helps clarify the model as well. It was very weird how x^ would sometimes end a lifetime and sometimes not.

22 replies

MModular

•Created by NickJJ on 12/30/2023 in #questions

Adding __takeinit__ makes a difference in assignment

Sneak peak from the next release's changelog:

- The `__takeinit__` special constructor form has been removed from the
  language.  This "non-destructive move" operation was previously wired into the
  `x^` transfer operator, but had unpredictable behavior that wasn't consistent.
  Now that Mojo has traits, it is better to model this as an explicit `.take()`
  operation on a type, which makes it clear when a lifetime is ended vs when the
  contents of an LValue are explicitly taken.

- The `__takeinit__` special constructor form has been removed from the
  language.  This "non-destructive move" operation was previously wired into the
  `x^` transfer operator, but had unpredictable behavior that wasn't consistent.
  Now that Mojo has traits, it is better to model this as an explicit `.take()`
  operation on a type, which makes it clear when a lifetime is ended vs when the
  contents of an LValue are explicitly taken.

22 replies

MModular

•Created by NickJJ on 12/30/2023 in #questions

Adding __takeinit__ makes a difference in assignment

Oh, I didn't notice that this was correlated to adding takeinit actually! Well that make sense why it is fixed 🙂

22 replies

Gaming

Programming