• 0 Posts
  • 66 Comments
Joined 7 months ago
cake
Cake day: November 26th, 2023

help-circle






  • It’s new to me, I think it’s saying that your system is built up by you declaring what you want in a file, a single source that everything comes from.

    It’s atomic because each action the system takes is carefully completed rather than bailing out and requiring you to fix something.

    It’s immutable meaning you declare how you want things to be set up and then critical changes stem from those declarations and nothing else. You would obviously generate preferences, save data, etc. but the files that make the system / packages work are carefully locked.

    It’s like the concept of flatpaks + structured system defining + modern common sense OS operations?






  • 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.worldtoProgrammer Humor@lemmy.mlThanks ...
    link
    fedilink
    arrow-up
    4
    arrow-down
    20
    ·
    1 month ago

    I don’t see a negative. It’s foss so you ought to be relaxed about others using your code. The issues are probably just articulating problems that were already there. If it’s stuff you don’t care about… it’s a foss repository so you just ignore it.



  • Based on the headline I got the impression that the bible was excluding these two amendments. As in, their absence was jarring in the presence of the other amendments.

    The truth is that they left out 17 amendments. Because it’s Trump. It’s aimed at people who don’t care about the Constitution. The customers just want the greatest hits, the big names.

    Misleading headline aside, here’s what the they actually omitted (aka here’s a truth which doesn’t leave anything out.)

    1. Can’t sue a state unless you live there.

    2. Structures electing presidents / VPs.

    3. Slavery is banned except when it isn’t.

    4. Born on US soil == you’re 'Merican, Harry.

    5. Suffrage regardless of race.

    6. Taxes.

    7. Structures electing senators.

    8. Prohibition good!

    9. Suffrage regardless of sex.

    10. Specifies length for Presidential / VP terms.

    11. Prohibition bad!

    12. The two term limit for Presidents.

    13. Gives D.C. electors.

    14. You can vote even if you didn’t pay taxes.

    15. Formalized the VP succeeding a dead president.

    16. Voting age set to 18.

    17. That time when Congress took 200 goddamn years to impose a restriction on their salary.