• 0 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: November 26th, 2023

help-circle

  • mhague@lemmy.worldtoMemes@lemmy.mlEnd the Imperialist Blockade
    link
    fedilink
    arrow-up
    1
    arrow-down
    3
    ·
    4 months ago

    All I ask for is the truth. That’s why I’m called tankie, liberal, Nazi, commie, Trumper, imperialist, hippie. I get bent out of shape when people sling lies and it causes me to become whatever boogeyman they’re turning around in their head.

    Did you comb my posts to figure out I’m a liberal? I’m pro India, pro USA, pro China, pro Russia, (making it simple so you can digest it) so it’s weird you got liberal.


  • mhague@lemmy.worldtoMemes@lemmy.mlEnd the Imperialist Blockade
    link
    fedilink
    arrow-up
    12
    arrow-down
    12
    ·
    4 months ago

    I’m flabbergasted that the official website of a political entity is being touted as evidence that the political entity isn’t perceived correctly.

    Forget about Cuba, or politics, or class, everything. This is not how you find the truth. What’s the thing I’m not thinking of that’s throwing things off balance? Why would someone link to North Korea’s official website to argue that North Korea is not so bad? What’s the use and whose it for?









  • You use lifetimes to annotate parameters and return values in order to tell the compiler about how long things must last for your function to be valid. You can link a specific input with the output, or explicitly separate them. If you don’t give lifetimes the language uses some basic rules to do it for you. If it can’t, eg it’s ambiguous, then it’s a compile error and you need to do it manually.

    It’s one of the harder concepts of rust to explain succinctly. But imagine you had a function that took strA and strB, used strB to find a subsection of strA, and then return a slice of strA. That slice is tied to strA. You would use 'a annotation for strA and the return value, and 'b for strB.

    Rust compiler will detect the lifetime being shorter than expected.


    Also, ownership semantics. Think c++ move semantics. Only one person is left with a good value, the previous owners just have garbage data they can’t use anymore. If you created a thing on the heap and then gave it away, you wouldn’t have it anymore to free at the end. If you want to have “multiple owners” then you need ref counting and such, which also stops this problem of premature freeing.


    Edit: one more thing: reference rules. You can have many read-only references to a thing, or one mutable reference. Unless you’re doing crazy things, the compiler simply won’t let you have references to a thing, and then via one of those references free that thing, thereby invalidating the other references.




  • mhague@lemmy.worldtoScience Memes@mander.xyzbugs
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    1 year ago

    It was a Google site (from years ago) so all that’s left is a random archive somewhere. I had all the local spiders+favorites, but the only original content were pictures of Latrodectus and Kukulkania Hibernalis. Beautiful spiders.


  • mhague@lemmy.worldtoScience Memes@mander.xyzbugs
    link
    fedilink
    English
    arrow-up
    22
    arrow-down
    1
    ·
    edit-2
    1 year ago

    I’m not a scientist, but I’m the kind of person to keep black widows as pets and create a website that catalogues all the spiders in my area. I’d allow spiders being called bugs, or even insects. Even poisonous is alright but it does hurt a little.