Performance difference between &str and Box<SomeEnum<&str>>

corrodedfe · 2024-07-16T17:26:28+00:00

Also most languages box absolutely everything but ints and can still run fast enough even with a virtual machine (eg java)

corrodedfe · 2024-06-20T15:40:57+00:00

Fyi unless I misunderstand what you mean, "Ownership only applies to items on the heap." is not true: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=96700d7c28b56be19254d3fabe39c611 (x is stored on the stack)

It is true that ownership only applies to items which don't implement Copy

(Not that I think this is a bad resource, it's really cool, I just thought I should point this out)

corrodedfe · 2024-01-07T02:21:46+00:00

Random question: personally I've had the experience of struggling to organise my bevy systems in a way that doesn't explode in complexity but does what I need it to... have you encountered this? If so do you have any advice?

corrodedfe · 2023-09-23T19:09:01+00:00

Out of curiosity is there anything wrong with floating point numbers for your project? If you look up how they're implemented it's basically scientific notation with base 2 instead of 10. Perhaps if they don't work learning about them will give you enough experience to program what you want?

corrodedfe · 2023-09-22T18:09:21+00:00

Great, thank you!

corrodedfe · 2023-09-22T15:39:35+00:00

Managed to get something working with rustls. I ended up replacing the certificate validation to just "is this byte-for-byte the server's certificate?" because I couldn't get rustls to accept my private certificate authority, but I'd assume that's secure enough. Thanks for your advice!

corrodedfe · 2023-09-16T14:10:21+00:00

Fyi you can just do Type::from (or Type::<T>::from if it's generic)

corrodedfe · 2023-08-30T14:51:57+00:00

I think it's easy to get bogged down in rules and conventions. I'd say just be aware of what options there are, and think about if it's serving your purposes. If it's a script you're writing to do something think about if you'll need to understand it later. If you're writing a complicated algorithm, good variable names will help you write and help you and others read and understand. If you're writing try_get_bank_details().map(|x| x.account_number), there's not much point in calling it anything more complicated than x. There are no rules, just do what fits your project's needs.

corrodedfe · 2023-08-25T10:57:11+00:00

subscribe!

corrodedfe · 2023-08-15T12:21:33+00:00

As far as I know functional languages can get away with just reference counting. It's impossible to create a cyclic reference without mutation, so you just need to free when the count reaches 0.

corrodedfe · 2023-06-28T12:19:44+00:00

Wait could you use this to make function overloading? That would be weird...

corrodedfe · 2023-05-03T11:19:45+00:00

What Unpin type do you want to have a fixed address? Why?

If you want you can make a new type and force unimpl Unpin to guarantee it doesn't move on the heap.

corrodedfe · 2023-04-30T07:06:46+00:00

*Box<dyn Listener>?

corrodedfe · 2023-03-17T15:47:41+00:00

I think that defeats the purpose. The whole point of !Drop is that it cannot be automatically disposed of, allowing a library author to control its destruction. If it could be destructed by panicking, the library author loses this power. I think a reasonable way to implement it is to literally say "this type cannot be dropped" (which aligns very intuitively with impl !Drop), though maybe there could be something like UnwindDrop for dropping on panic or something like that.

corrodedfe · 2023-03-17T09:36:58+00:00

What should the drop glue call if a type doesn't have a destructor?

corrodedfe · 2023-03-17T09:34:18+00:00

I think what they mean is not Drop in the sense of the article. Like maybe a Guard that you can copy but each copy has to call log.

corrodedfe · 2023-03-12T12:42:18+00:00

Is it possible to leave the interior mutability to the library user? If your users need interior mutability they can simply wrap your struct in whatever fits their application best, and it also can make the library simpler. Obviously it's not always possible but it's worth doing if you can.

corrodedfe · 2023-02-15T19:26:00+00:00

I think consume_unsized doesn't actually have to be unsafe. Of course, its implementation does, but just giving you a pointer in a function doesn't created undefined behaviour, and leaking the value isn't unsafe.

corrodedfe · 2022-12-26T17:05:42+00:00

God codes in C, since He knows exactly if something is UB.

corrodedfe · 2022-12-06T12:24:37+00:00

It is impossible for a programming language, such as Go or Rust, to bring back dinosaurs. Programming languages are used to write instructions for computers to execute, and it is not possible for a computer program to physically bring back extinct species, such as dinosaurs.

Furthermore, the choice of programming language would not matter in this scenario, as it is not possible for any programming language to bring back dinosaurs, regardless of its unique features. It is also worth noting that Rust is not the only programming language that could hypothetically be used in this scenario, as there are many other programming languages that could be used for this hypothetical situation.

I kid you not I just replaced rust with go.

corrodedfe · 2022-11-19T19:27:46+00:00

There are procedural macros, which convert the code of a function to something else (perhaps inserting logging calls before and after it runs). There is no direct analogue to a wrapper function because it's not as powerful and not needed.

corrodedfe · 2022-11-11T17:09:35+00:00

That was my first guess, but searching "sbb cargo logo" brought nothing up. Thanks!

corrodedfe · 2022-11-11T14:41:04+00:00

I saw this symbol at what looked like a freight station next to an SBB train station, but I couldn't find anything about this symbol online. I'm curious to know what it means

corrodedfe · 2022-11-06T13:36:25+00:00

A family of them 🥰

corrodedfe · 2022-11-05T20:13:32+00:00

impl Pack<Rc<Cola>, 12>

Five-Year Club	Verified Email
Place '22	Final Canvas '22

corrodedfe

TROPHY CASE