What do you hope will be supported in the next version of Mojo 🔥 0.7? Share your opinion with us

[Eprahim-taha]

I hope that lifetime will be supported in the next version of Mojo 🔥 What about you? What do you hope will be supported in the next version of Mojo 🔥

[rarebreed]

Lifetime/references

I've been holding off on really programming much with the language beyond simple toy exercises, because references will I think, be a pretty drastic change to how you need to think about coding in mojo.

I sincerely hope that mojo won't allow coding with raw Pointer types, because honestly, I don't want to deal with segfaults and other memory nightmares. It will need some way to give access to them, but I don't want willy-nilly access to an unsafe pointer type. If mojo does allow indiscriminate unsafe programming, I'll probably stick with rust and use some SIMD optimizations hacks along with Godbolt.

I'm actually a little concerned that mojicians will get too comfy programming with raw pointers, so the sooner mojo has a way to pass around references and lifetimes the better. One reason rust really caught on, despite the learning curve, was that it was ultimately easier to learn, and far safer than C++.

The next thing I want in mojo after lifetimes are Algebraic Data Types. Traits are relatively simplistic right now without a Sum type. Also, ADT's will give you the ability to return Option/Maybe types. While I know mojo has to support Exceptions, it's far more elegant and simpler to have functions that return some kind of Sum (with a Functor-like trait) type.

[felixf4xu]

I would like the support of python keyword argument, as tracked by this issue: #964

Many python functions have many arguments, in python it is not an issue since keyword argument can be used. But when mojo calls python code, it's pain to provide the entire argument list while most of them are optional.

[trongnamdz1]

You damn right, still waiting for a fixing up.. smh

[Brian-M-J]

I would like the support of python keyword argument

In version 24.2, it's now supported:

Mojo's Python interoperability now supports passing keyword arguments to Python functions

[jayzhan211]

Synchronization primitives.

Python https://docs.python.org/3/library/asyncio-sync.html
Golang https://pkg.go.dev/sync
Rust https://doc.rust-lang.org/std/sync/

[RichardoZhao]

I'd like to unsubscribe this project, cause my emailbox has been fed up with all the discussion.
So, I need help, wiill any friend tell me how to achieve that?

[rarebreed]

I'd like to unsubscribe this project, cause my emailbox has been fed up with all the discussion. So, I need help, wiill any friend tell me how to achieve that?

@RichardoZhao Once you are logged into github, go here
https://github.com/watching

Look for modularml/mojo and to the right should be a button "Unwatch". If you click that, you can either select Ignore, or you can click Custom, and choose which events you will be notifed on (for example, you can deselect Discussions and Issues).

[Brian-M-J]

True Windows support without the need for WSL.

[soraros]

@Eprahim-taha What do you mean by Mojo doesn't support Intel? It runs on Intel based system with Linux just fine.

[Eprahim-taha]

are you sure

[felixf4xu]

@Eprahim-taha What do you mean by Mojo doesn't support Intel? It runs on Intel based system with Linux just fine.

he means macos, intel version (old mac) is not supported yet, only arm M1 M2 versions are supported

[soraros]

@felixf4xu Could be. However, that doesn't explain their doubt("are you sure") for my claim "It runs on Intel based system with Linux just fine." which doesn't have the macOS ambiguity. Nor does it explain their assumption that support for Windows(native) somehow depends on support for macOS(Intel). For instance, I have no problem believing that some work on Linux(Intel) and macOS(ARM) can be reused for macOS(Intel).

[felixf4xu]

On Jan 28:

[manatlan]

I'd like a fix on this perf issue : #1216

Because mojo is still slower than go, rust, nim .. and still slower than java, nodejs, pypy and codon
https://github.com/manatlan/sudoku_resolver/blob/master/RESULTS.md

(With the good old "0.4 mojo version" : it was 10x faster)

[alfie-nsugh]

I want support for nvidia gpus

[rarebreed]

I want support for nvidia gpus

I don't know if that will be in the 0.7 release, but according to the Keynote, that will be available once the MAX Engine SDK is released. Which if I remember correctly, they said should be coming out in first quarter of 2024

[stefanuytterhoeven]

Well, concurrency,parallisation is supported. I would like to see examples,examples and examples!
Also some kind of list like 'in python you do this', in mojo it's done like that...

[alfie-nsugh]

I completely agree with this. Having some centralised place where you have a bunch of examples would be great. It would greatly speed up learning

[manatlan]

I've updated my code&results on my repo : https://github.com/manatlan/sudoku_resolver (differents implems of a sudoku resolver, to compare with others languages)

The spezialized one is quicker ... the simple one is slower ;-(

[l1t1]

it works on aarch64 Android+termux+proot-distro Linux