5

RustConf 2021 - Project Update: Lang Team by Niko Matsakis

 2 years ago
source link: https://www.youtube.com/watch?v=ylOpCXI2EMM
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client
0:00 / 33:03

RustConf 2021 - Project Update: Lang Team by Niko Matsakis

7,547 views
Sep 15, 2021

33.7K subscribers

Project Update: Lang Team by Niko Matsakis

2021 has been a very exciting year for Rust. In addition to the upcoming release of Rust 2021, we saw the formation of the Rust foundation along with the creation of a number of teams dedicated to Rust development. Rust is even being considered for the linux kernel! Nicholas will talk about what all this means for Rust, and what we can expect to see as Rust moves ever closer to its goal of “empowering everyone to build reliable and efficient software.”

Show lessShow more

9 Comments

Sort by
default-user=s48-c-k-c0x00ffffff-no-rj
Add a public comment...
Not that my vote means much, but passing along anyways => I would vote for keeping "mut" on the binding. It's really good way to see when someone is creating side effects when they shouldn't be. On a somewhat side topic, one other thing with "mut" I was thinking about a while back is what if that could be used to instruct the cpu to cache in a read-only 'cache line' for variables that are not mutated (regardless of whether marked with mut). This way, less cache invalidation occurs because all muts are packed together and all non-mut are packed together. Idk if the cpu can be directed in that way, but if not currently, that might be a proposal for cpu makers, and the llvm project. Maybe they already do this though - it was just a passing thought. I suppose this thought could be related to any language if compiler can figure out if variable gets mutated or not.

Read more 3 weeks ago (edited)

Amazing talk, thanks Niko! I'd argue that Rust can have a positive environmental impact on CO2 emissions and be the number one programming language for Greentech.

2 weeks ago

Thanks Niko for the talk and all the hard work.

I would also argue for the "mut" keyword, or some different explicit way of denoting mutability.

3 weeks ago

I also would like to express my voice and mention that I think keeping "mut", for the same reason Jeff stated below.

2 weeks ago

Really happy to see that sense that Rust is doing well but that its not there yet in terms of usability (I agree with that sentiment as someone coming from c++ who is also familiar with languages such as python). I'm curious where are the best places to give feedback to the rust lang team about what is working vs what isn't in terms of usability? (Also a huge thank you to Niko and the Rust team for all their efforts making a great language that hopefully becomes the c++ replacement I hope it will be)

Read more 3 weeks ago (edited)

How about rust borrow visualiser to make it easy for developers

2 weeks ago

to me it seems that languages with lots of convenient syntactic sugar (eg. Python, Kotlin) get popular, despite not having real advancements (HM, control flow analysis, safety guarantees etc) and/or inheriting the limitations of the parent language. if you can write with(object) and you don't have to type the object's name 10 times, it doesn't matter anymore that a hello world allocates 3 gigs.

Read more 3 weeks ago


report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK