Yo whatup
Wealth issue (not really shits cheap)
Permits is only required when the compiler can’t see the extending classes. IE inner classes can extend without needing to be written out in a permits
clause. This isn’t really that useful but I’ve taken advantage of it more than once so who knows
It’s complicated. Paul isn’t really a good guy, but he’s not really a bad guy either. He’s just a dude. He’s a dude who has limited vision into the future from which he cannot escape. He’s not using his future vision to pick the bad choices he’s trying to pick the best ones he can and the hand he’s dealt kinda just sucks.
Nah bro that’s just the memory leaks, your supposed to force close and reopen it every so often so the OS cleans up after their shitty application
Um what? I didn’t like hide extra meaning in what I said. High quality code doesn’t imply all that extra shit you added. It’s code that’s easy to read and modify. Typically this just means you name stuff well and document things that aren’t obvious. Usually my docs explain why something exists since thinking it’s unnecessary cause you don’t remember what the original problem was a common occurrence before I started doing so.
Is high quality code ran through a formatter? I’d hope so yeah. There should be a consistent code style across the entire project. Doesn’t matter what it it long as it’s consistent.
100% code coverage is meaningless and as such a pointless metric. Also 100% coverage is explicitly tied to the implimentaion as all code paths have to be reached which is obviously not a good idea (tests have to change when the implimentaion changes as you’re testing the implimentaion not the api).
Really a lot of this is just meaningless buzz words as an attempt at some sort of gotcha. Really don’t understand how you even interpreted a statement so simple in this way.
Ah sure, like scripts and stuff. I have some absolutely atrocious python hanging out to help me do shit. I don’t have like any actual projects that are just a trash fire though
I don’t really get the code point. Like your own code written for personal projects is probably gonna be pretty high quality I’d hope? Sometimes we just write trash to get something finished but soon as I’ve had to change it… hell yeah I’m unfucking that mess, no way do I want to figure out what it does a second time.
ReVanced is a modded YouTube (and others) app. IE normal YouTube but you fuck with it locally to skirt what got the original Vanced guys. Adblock, OLED black theme same old thing Vanced provided. I’ve used NewPipe very little but I’d summerise a comparison as ReVanced has better user experience (thanks to Google making the app) and you can sign in/get notifications ect
There’s a couple grifters who pretend (or are stupid enough) to think so yes. It’s like the “doctors” the anti vax guys point at
I’d probably say it depends but I’m no Rust expert and I have no direct experience with C (though quite familiar with C++).
Basically I’d expect writing C to be easy, but not safe. IE you can quickly and easily write C that compiles but has runtime issues. Rust for the most part will catch everything but logic issues during/before compilation meaning once the program runs you’ll have very high confidence in it’s runtime behavior leading to time spent “fighting the compiler” instead of figuring out wtf is going wrong at runtime.
Yes Rust is harder to write than C, that’s basically by design as it’s due to the statically guaranteed memory safety. That’s pretty magical. C doesn’t have that and neither does C++ even with smart pointers and such. Rusts unsafe keyword is poorly named, what it actually does is tell the compiler that you the programmer guarantee Rusts rules are upheld within the unsafe block.
For example
Access or modify a mutable static variable
That is a global, that’s incredibly hard to impossible to statically prove it’s safely done, so you have to do it in an unsafe block. So you violating Rusts rules within an unsafe block is actually using the unsafe block wrong. That’s not what it’s for
Unsafe Rust really just let’s you play with pointers
This is the entirety of what Unsafe Rust allows
Incredibly I don’t think that the USSR is “as bad as the Nazis” nor did I say anything like that. Is that why you morons are calling me a Nazi? Do you guys need a paragraph explaining that yes I do think the Nazis are bad?
I’m not trying to win fuckn internet points I’d still be on reddit if I got turned on by that kinda shit. You people are.
I read it before I’d even replied. It’s got nothing to do with the USSR being facist or not.
Yeah despite how much I want to fight back I know I’ll just be wasting my energy
How do holocaust scholars relate to the USSR being facist or not? Facist ≠ Nazi though fascism leads directly to the kind of ideas the Nazis hold
Saying that Facists are Facists is trivializing the holocaust? How’s that work? The fact Nazis were Facists doesn’t trivialize the fact that other groups are also Facists. Facists like to kill people that’s kind of their whole ideology. Fascist ideology leads directly to the kind of ideas the Nazis had.
Ah shit. Guess you can tell what kinda stuff I like watching
So the big important part of git is that it’s a collection of commits. A branch is just a labeled commit and each commit is a list of what changed from the parent. Rebasing (the most confusing one for people) is when you fiddle with a commit from underneath yourself. Or in even more simple terms editing a parent commit. Rebasing is extremely powerful but most useful for when you notice a bug you wrote a couple commits ago. Fixing such issues via rebase (or
!fixup
commits you auto squash at the end) keeps your history clean. It’s as though you never wrote the bug. The other thing you do a lot with rebasing is moving your branch up in the history cause somebody updated the remote.