Rust

6005 readers

4 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

EdTheLegendary@programming.dev

kahnclusions@programming.dev

torcherist@programming.dev

Should I Rust or should I Go? (kerkour.com)

submitted 1 year ago by eraclito@feddit.it to c/rust@programming.dev

21 comments fedilink hide all child comments

I think some raised points are relevant...

you are viewing a single comment's thread
view the rest of the comments

[–] Turun@feddit.de 1 points 1 year ago* (last edited 1 year ago) (4 children)

I think they introduce new keywords every now and then. Match and async I think?

Edit: I was wrong, this is done in a backwards compatible manner

[–] UlrikHD@programming.dev 4 points 1 year ago (3 children)

Those doesn't break backwards compatibility though. Naturally you can't use match with a python 3.7 interpreter, but what scripts written for python 3.7 wouldn't work with a 3.11 interpreter?

I haven't encountered that issue before, so I'm curious what those problems OP have encountered looks like.

[–] Turun@feddit.de 1 points 1 year ago (2 children)

Huh, ok. I thought something like match = 0 in an old script might break a more recent version.

But you may very well be correct.

[–] UlrikHD@programming.dev 1 points 1 year ago* (last edited 1 year ago) (1 children)

match isn't a protected keyword like if is.

match = 0
match match:
    case 0:
        print(0)
    case _:
        print(1)

Is legal and will give print out 0.

[–] Turun@feddit.de 1 points 1 year ago

Well, today I learned. Thanks for pointing it out.