

oh jeez! yeah that makes sense will add them to constructor thank you!
oh jeez! yeah that makes sense will add them to constructor thank you!
Ah good to know just using tabs in vim but in two different machines so might be the issue— thanks!
Aha ok yeah that does make more sense will give it a shot— thank you!
Let’s say I’m using a streaming service for instance
Seriously helpful thanks! One of my friends working on a G15 restoration project pointed out this notation to be after you did— yet while they use 0 for truth they used 20 for false so not sure were they got the second idea. And your vim tip saved me a bunch of hand ache!
Yeah that’s fair— this is my focus workstation so don’t have any messaging apps or email to send the screenshot but def could have taken a second picture.
I guess in reading not until c99(see other comment); they just used integers in place of Booleans, in which case your readability statement makes more sense given the historical context
I’m not sure I understand readability? I guess is disambiguates numeric variables if you used 1 and 0. But with true and false available that would seemingly do the same thing. You still have to know what the arguments your passing are for regardless.
Ahh this makes some sense
Hmm I can’t decide if this is a joke or if I’m just very privileged in the internet department
I remember back in 2013 I picked up the full expansion set at a thrift store for $4 it was the best summer of middle school by far— got the werewolf mod working and went around finding out who was essential to the plot by killing them and then reverting the saves— good times
Can it be running some unix derivative?
Thanks for the tip! https://github.com/jcuberdruid/DeepBlue
I’ll add more to the repo but here it is for now :)
Not just yet but it’s in the works!
Thanks! I made a submarine game called DeepBlue where you explore the ocean floor generated by ocean depth map data:
I do really like the error system in rust for its descriptions. I guess the difficulty for me, which maybe will go away after writing more rust, is that my intuition for what is efficient and what isn’t totally breaks down.
I find myself passing copies of values around and things like that, it might be that the compiler just takes care of that, or that I just don’t know how to do it well but that’s often the point of friction for me.
Totally agree on the refactor though, most of the time it doesn’t even take that much time since you know the skeleton of what you want at that point!
Maybe it’s just because I haven’t had to deal with the scenario yet but does compile time really matter? I mean for small programs it seems it’s almost instant on modern machines and for large programs I would assume, if it exists, that you would be using the equivalent of make so you would only be recompiling the small changes made.
deleted by creator
Also Swift!
Ah yes I see! That should offer some improvement given the number of times it’s called— also see I’m used to swift so I keep using let when I should probably use const— thanks I’ll give it a try and let you know what happens!