Видео

Debug vs release executable size is mind blowing!

Great effort

reupload this ,audio is bad even tho the video is good :)

I've started using closures more and more in my code. There really powerful and just as fast as function pointers.

Please make a video on how what changes to make to make it work live and how to make this work with typescript .

What font are you using?

you lost me as soon as you opened NV,

You don't really need to implement the "from_array" method. I mean, you can, but it always seemed a bit redundant to me. There is a shorthand when using the map function on iterators if the operand signature matches the item type in the array: ``` let vehicle_array: [u32; 4] = [1, 2, 3, 4]; let vehicle_vec = vehicle_array.map(Vehicle::from); ``` So it's kinda simple without the extra method. And if you really wanna be all "fancy" and add a variadic version of the function (a function that accept an arbitrary number or parameters), you can create a macro like this: ``` #[macro_export] macro_rules! vehicle { ($($num:expr),*) => { [$(Vehicle::from($num)),*] }; } ``` Which allows you to call the function with any number of variables and get back an array like this: ``` let vehicle_vec = vehicle!(1, 2, 3, 4); ``` My approach is usually to implement as little functionality as possible to a struct. But that's just me, it's not necessarily a good or bad practice, I just like my API's as small and lean as possible.

which editor/IDE are you using ?

Great video again. What would the benefit of impl Animal for the structs rather than just using it on the enum? impl Animal for PetType { fn make_sound(&self) -> &str { match self { PetType::Catly => "miaow mieew", PetType::Dogly => "bow wow wow", } } }

the difference in timings could be because of the println!() macro maybe? what if you try the same but you do not print at line 3 and 10?

I would recommend not using short names or acronyms. It might seem "neater" at first, but if you have to think for even a split second about what something is, you are slowing down yourself and anybody else who reads/works on your code. Use names that are clear everywhere that variable/function/etc is used. It's annoying to have to keep scrolling back up (or jumping between files) to see what "dbaf" means, especially if you are coming back to this code 6 months later because you need to fix something or add a feature. Naming things is the hardest but most valuable skill in programming, no joke.

Oh My God!! Someone actually using match in a demo.

Is one action more expensive than the other?

Dam just realized that I have actually never learned how to do this in rust thanks.

I completely agree that you have to go over Rust again and again

Please make video series on dioxus desktop app with surrealdb embedded..

great video man, thanks for sharing this

Really cool video thank you for sharing! I've been working heavily with Leptos which has 0.7 coming out within the next month or so, would be cool to see a video covering the release notes perhaps :D

Not the entirely unrelated AI woman in the intro 😭

Nice! Please come up with videos on dioxus GUI and it's integration with embedded surrealdb .

nice! thanks for this

agreed - nice book; subbed

Since the dawn of time the pointer to the next node in a linked list has been called "next". No confusion there.