I poo almost daily at work. It’s almost impossible to hold it in for 8:30 continuous hours.
If someone tells me off for it, they will find out how much my productivity drops when I have to focus on holding the shit instead of doing my work.
Poo in work. Not only is it a nice break, but it also is more productive than not pooing. Win-win for everyone.
To be fair, in that article mentions the way to get rust from C. Sure, there is not a compiler written in C, but C is down there in the list of compilers needed for rust, so “just” need to compile some other compilers in the middle.
The bedrock of modern civilizations is expensive to develop, buggy and unergonomic though.
If you make C run, you probably (I’m not sure, would have to verify) can make rust run. And if there isn’t yet, there will probably soon be a C compiler written in rust, so you can choose to bootstrap from wherever you prefer.
C’s ABI will probably last longer than C, since there is not a stable rust ABI though.
Shouldn’t being a convicted felon affect one’s candidacy?
Should the US government also pay candidates to have aesthetic surgeries? Being ugly might affect their candidacy!
I believe the game was 10 days old when they shut it down. There are no concord fans. You can’t have fans in 10 days.
My guess is that they knew it was going to be a shit game, but realized too deep in the development phase. So they just released it as soon as possible and didn’t waste more money on it (marketing). My guess is that the released it instead of cancel just in case they were wrong and people actually liked it.
To be fair, mechanic items, and especially electronic ones were far more repairable back then.
You could see, desolder and solder components without issue. Nowadays most of the electronics are inside chips, and only the components that need to be physically big (like those responsible for the power supply) are human sized. Sure, there are some small SMD that can be manually diagnosed and replaced, but even then you often need a lot of skill and equipment.
The good thing about Box::leak() is that it returns a raw *mut pointer. So you need unsafe{} to dereference it. Might as well: let my_ref = &mut unsafe{*ptr}; while you are at it, so you have a perfectly normal rust reference, so the function signatures don’t need any change.
The problem with Rc is that it would also require a RefCell most of the time. So the whole thing would be filled with Rc<RefCell<T>>. With the required .borrow_mut(). It would both do a pain to do and undo.
And of course I want to undo it, because RC is a shitty GC.
I’ve re-thought about the problem and I think for prototyping I should just Box::leak() and work with raw pointers.
This approach also doesn’t allow you to not learn the borrow checker, since leaking everything is not a good memory management strategy, but might be fine for rapidly iterating on a design.
EDIT: maybe use a leak!() Macro that does Box::leak(Box::new()) in debug mode but panics on release (as long as you execute once in release it should be fine).
Another user already proposed Odin, but no one yet Jonathan blow’s unnamed programming language (people call it jay). Those are the 2 programming languages that came to mind when I think of game development.
I haven’t tried either so I don’t know if they fit you, but they are new languages so they should avoid java’s and C++'s pitfalls.
Interfaces (traits in rust) are the best imo. Way better than raw structs in C or the mess that is inheritance.
What I don’t like about go’s interfaces is that they’re implemented implicitly. I much prefer java’s and Rust’s way to implicitly say which classes/structs extend/implement which interfaces.
Using “clever” ways to disable the borrow checker is one of the few things I don’t like about rust. I much rather it having a “borrow checker version” and a “garbage collector version”. That way we could rapidly iterate through design choices with the GC, and once the design has proven good, apply lifetimes and such to use with the borrow checker. The only downside to this I can think of is that most would just leave it in the GC version and not bother to move to borrow checker. But that’s fine by me, rust has many other features to take advantage of. As long as no GC libraries are allowed in crates.io, it should be fine.
You can just. Have datastruct be mutable if you want. Immutable by default doesn’t mean you can’t make variables mutable.
Of course younger generations are more likely to believe in pseudo science, they haven’t yet learned that they are bullshit. Once they get older and have more experience with detecting bullshit, it’s popularity should decline.
My favourite is when every error is an HTTP Bad Request with no body. Absolutely wonderful to use those APIs
Do you want north Korea itself to report these news? Of course reporting them is those that are interested in reporting these news.
It doesn’t mean that the news are real, but it doesn’t mean that they’re fake either.
Yeah because Winnie the Pooh is an American propaganda machine. Show me a quote of xi jumping saying that it is because he doesn’t like being compared to a cartoon bear!
(I’m cosplaying as a lemmy.ml)
Fold it twice, still free