正在加载视频...

视频加载失败

Everyone is writing the TypeScript compiler in rust. I wrote the rust compiler in TypeScript. Introducing “cargovroom” a rust compiler built fully in typescript.

63,385 次观看 • 8 天前 •via X (Twitter)

33 条评论

Neesh 🥭 的头像
Neesh 🥭8 天前

now rewrite it in rust and then compile it again

Noah 的头像
Noah8 天前

Blasphemy

Neil Chudleigh 的头像
Neil Chudleigh8 天前

now make it slower

maria 的头像
maria8 天前

does it compile faster?

Noah 的头像
Noah8 天前

yes somehow

PaulPlay 的头像
PaulPlay8 天前

Now run it through scriptc, and maybe it's faster than the original ;)

Can Vardar 的头像
Can Vardar8 天前

but can it cook for me?

Pranjal Paliwal 的头像
Pranjal Paliwal8 天前

you must be fun at parties

Yuri 的头像
Yuri8 天前

does it have borrow checker?

BreezeOg 的头像
BreezeOg8 天前

the reverse uno 😭

Justin Torre 的头像
Justin Torre8 天前

Lolol

Cupsey 的头像
Cupsey8 天前

a rust compiler in typescript. the circle is complete

0xDE, 0xAD, 0xBE, 0xEF 的头像
0xDE, 0xAD, 0xBE, 0xEF8 天前

I’m so poor bro 😭

Parth Bhosle 的头像
Parth Bhosle8 天前

I mean u could've just did exec(`cargo ${subcommand}`)

Daniel Vélez 的头像
Daniel Vélez8 天前

where's the repo?

dpc 的头像
dpc8 天前

Can it compile Rust itself? Unironically could be useful for bootstrapping.

Greg Schier 👨🏼‍💻🇨🇦 的头像
Greg Schier 👨🏼‍💻🇨🇦8 天前

Can't be slower than it is already

Dimava 的头像
Dimava8 天前

Does it just compile or typechecks as well?

UPDOG 🇬🇧🇯🇵 的头像
UPDOG 🇬🇧🇯🇵8 天前

astounding

Arihant 的头像
Arihant8 天前

hell yeah

Jephthah Mbah 的头像
Jephthah Mbah8 天前

This is getting out of hand

fiona 的头像
fiona8 天前

Kys

Amar AlAzizy 的头像
Amar AlAzizy8 天前

Is it rust or go or native ts?

shїneq 🇵🇱🇺🇦🇵🇸🇬🇪 的头像
shїneq 🇵🇱🇺🇦🇵🇸🇬🇪8 天前

Cursed

Arpit 的头像
Arpit8 天前

Time to write everything back to ts....

OthmanHaba 的头像
OthmanHaba8 天前

the most rusty thing i ever saw 🦀

Aaron 的头像
Aaron8 天前

lmao

Andhrimnir @ Lan Game Studios 的头像
Andhrimnir @ Lan Game Studios8 天前

if gpus had feelings they would be very upset right now

Hong Truong 的头像
Hong Truong8 天前

Can it compile bun?

Sumit Datta 的头像
Sumit Datta8 天前

But, are you using tsrs to compile the Typescript code? Loop-di-loop

Cyberistic 的头像
Cyberistic8 天前

awesome name

Riley David Jesus Seaburg 的头像
Riley David Jesus Seaburg8 天前

Please tell me this is a joke how do people have the time or money to do this?

Fahreza 的头像
Fahreza8 天前

Therefore the downside in rust development is no more?

相关视频

Why is Rust different than many/most programming languages? Alice Ryhl works on Google's Android Rust team, is a Rust language team advisor, and is a core maintainer of Tokio (the most widely-used async runtime in Rust) Timestamps: 00:00 Intro 04:09 Tokio: an overview 05:11 What Alice likes about Rust 12:48 Rust for TypeScript engineers 13:51 Moving from C++ to Rust 14:34 Memory safety 18:12 Garbage collection tradeoffs 21:46 Ownership, references, and borrowing 26:59 Unsafe in Rust 31:21 Crates and Cargo 35:55 Language design and RFCs 43:02 Building new features 46:30 Editions vs. versions 49:47 Getting paid to work on Rust 51:27 Contributing to Rust 53:03 Rust in the Linux kernel 55:45 AI use cases for Rust 1:01:35 Learning Rust 1:03:54 Book recommendation Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. • Sentry – application monitoring software considered “not bad” by millions of developers Three things worth knowing about Rust: 1. Rust was designed to turn implicit failures into compile errors. Where other languages allow you to forget something, Rust makes an omission into a compilation error for things like null checks, uninitialized variables, or error propagation with the ‘?’ character. If you mess something up, it’s almost certain your program will not compile. If it does, at the very least you should see a lint warning. 2. Refactoring in Rust is safe and easy, thanks to the compiler. Alice: “I change a return type or struct field, then just fix the compiler errors until the compiler stops shouting. And then once I’ve done that, I’ve updated every place I need to update.” Rust’s focus on correctness makes refactoring it more straightforward than dynamically-typed languages and Java-style typed ones are to refactor. 3. “Editions” allow Rust to make breaking changes without ‘breaking’ anyone’s code. Rust editions (2015, 2018, 2021, 2024) can be mixed freely across crates. A library on the 2021 edition works seamlessly with a binary on the 2024 edition. This is how Rust evolves syntax (like adding async/await as keywords) without forcing an ecosystem-wide migration. Thanks a lot, Alice for this great discussion! And for your work on Rust.

Gergely Orosz

52,449 次观看 • 5 个月前