chrislattner

7 ms·

31.
by chrislattner 3y ago
I'd love it if you could ask technical questions on the discord channel, as that's more scalable for us. Some quick answers: 1) We're likely to change the reference syntax to inout: https://github.com/modular
32.
by chrislattner 3y ago
We are a bit overwhelmed at the moment, but sure, this is something we'd eventually give an llvm devmtg talk about or something. Broadly speaking, there are three kinds of things that matter: 1) Type system. If you go with a constrai
33.
by chrislattner 3y ago
I have literally the same experience about slow and overly complex type systems and too much sugar as you're pointing out. I've learned a lot from it, and the conclusion is "don't do it again". You can see a speci
34.
by chrislattner 3y ago
I'm a fan of optional and other algebraic datatypes, you don't need to convince me. It's in our roadmap doc! :-) OTOH, Swift has way too much special purpose sugar which I'd prefer to reduce this time around, there are
35.
by chrislattner 3y ago
We're not in a rush here, we'd rather do things right than do things fast. Mojo is currently one day old :-) We are deliberately rolling things out in a slow way to learn as we go. We're also eager for it to go far and wide
36.
by chrislattner 3y ago
Mojo has a full ownership system that learned a lot from Rust and Swift and took the next step. Some details here if you're interested: https://docs.modular.com/mojo/programming-manual.html#argume...
37.
by chrislattner 3y ago
Check out the FAQ: https://docs.modular.com/mojo/faq.html#distribution
38.
by chrislattner 3y ago
Indeed, you're totally right about that. That's the trick with Mojo, our goal is not to make dynamic python magically fast. Yes, we are quite a bit faster at dynamic code (because we have compiler instead of an interpreter) but
39.
by chrislattner 3y ago
What's the question? They are sharp and pointy and Mojo has an unsafe `Pointer` struct vended by the standard library for folks who know what the they are doing.
40.
by chrislattner 3y ago
I can't speak for others, but I think fast.ai is pretty great...
41.
by chrislattner 3y ago
Thank you Keno!
42.
by chrislattner 3y ago
Hey VancouverMan, I'm sorry you're disappointed. We're still just at the start of this journey, not the end. Mojo is still quite young, and while we have high expectations (and a lot of experience in doing this sort of thin
43.
by chrislattner 3y ago
Yep, they already just work, Check the website or the demo in the launch video from Jeremy Howard. Also potentially interesting: https://docs.modular.com/mojo/programming-manual.html#python... https://docs
44.
by chrislattner 3y ago
Open source over time as it matures: https://twitter.com/Modular_AI/status/1653439606522802176?s=...
45.
by chrislattner 3y ago
Thanks for your interest, I'm pretty confident we can do this. I've been working on compilers and languages for awhile. :) Your point about LLVM compile time is great one. Mojo is architected from the beginning for fast compile
46.
by chrislattner 3y ago
Mojo fully supports arbitrary library designed types, check out the note books for examples that define custom matrix operations of various types.
47.
by chrislattner 3y ago
There are a bunch of questions about Julia, so I'll do my best to give a short answer to a very long and complicated topic. Up front, Julia is a wonderful language and a wonderful community, I am a super fan. That said, Mojo is a comp
48.
by chrislattner 6y ago
I agree for part of it at least, see this writeup which is directly related to Send: https://docs.google.com/document/d/1OMHZKWq2dego5mXQtWt1fm-y...
49.
by chrislattner 6y ago
It's impossible to cover "all the things" in one podcast. However, I'm happy to answer specific questions if you have a specific interest.
50.
by chrislattner 6y ago
Really sad to see how much of the commentary here is meta-commentary about Lex and not about the content. Several people asked, so here's the reason I chose to go on his show: it's because I love his work (frequent listener) and
51.
by chrislattner 7y ago
You're right - BB arguments are more general than LLVM-style PHI nodes. They are a strict superset, but are otherwise isomorphic for the cases they both support. The talk we gave at CGO yesterday includes a few slides talking about th
52.
by chrislattner 7y ago
https://twitter.com/JeffDean/status/1222033368700706816
53.
by chrislattner 7y ago
Yeah, I don't expect people to understand how transformative SiFive is. Give it a couple years and it will make sense :-)
54.
by chrislattner 7y ago
Google is pretty committed to it, don't take my word for it, take Jeff Dean's: https://twitter.com/JeffDean/status/1222033368700706816
55.
by chrislattner 7y ago
With the benefit of hindsight, I'm really happy both that I joined Tesla and also that I left it. I have no regrets at all. I learned a lot while I was there, but Elon and I had different opinions about some things. It was clear th
56.
by chrislattner 8y ago
The MLIR project has no plans to reimplement X86 or ARM backends. The LLVM Code generator could be improved of course (e.g. through the GlobalISel project) but there is no need to do that in the context of MLIR - MLIR supports codegen thro
57.
by chrislattner 8y ago
Thank you for the kind words Keno. We don't have a great description of what the polyhedral dialect is, but we do have a discussion of what it isn't, here: https://github.com/tensorflow/mlir/blob/mas
58.
by chrislattner 9y ago
As DannyB mentioned in his post, Google is very technology driven, not usually driven by zealotry. Using Swift for this purpose has specific technical motivations that will be spelled out in the white papers we are publishing in April. -Ch
59.
by chrislattner 9y ago
The key thing here is that the Swift compiler is computing gradients using SCT techniques, not TensorFlow. This has a number of advantages that we'll go into in the white paper we are going to publish in April, so I'd prefer to w
60.
by chrislattner 10y ago
I'm sorry if it came across that way, I have a ton of respect for Rust and the Rust community. I was just trying to say that its design forces discussion of the ownership model to be very early on in the description of the language. I

More ›