• 1.8K Posts
  • 6.92K Comments
Joined 3 years ago
Cake day: April 27th, 2023
  • SorteKanin@feddit.dkOPtoRust@programming.dev•What does it take to ship Rust in safety-critical? | Rust Blog
    1·
    10 hours ago

    I don’t agree with the comment there. In my mind, the LTS release would not mean anything. It would just be a label on an arbitrary release every couple of years. I feel it could help the ecosystem align on which MSRV to choose, so that you don’t have one crate choosing 1.x, another chooses 1.(x+1) and another chooses 1.(x+5). It would be nice if we just sort of agreed that if you care about your crate being used by somewhat older compilers, use the LTS version and consider the implications if your MSRV go beyond that version.

    Of course any crate author is free to completely ignore this and choose whatever MSRV they desire. But perhaps a significant amount of authors would put at least a little effort (but not much) in trying to avoid raising the MSRV above the LTS version, just as authors may try to avoid breaking changes and such. It’s just a nudge, nothing more.

  • SorteKanin@feddit.dkOPMtoNyheder@feddit.dk•Løkke og Motzfeldt får ros efter historisk møde, men 'man må jo håbe, at det holder'
    6·
    16 hours ago

    blot er en forhandlingstaktik

    Jeg tror nærmere det er en ego-ting for Trump. Han siger de skal have Grønland for national sikkerhed - i virkeligheden skal de have Grønland for at sikre Trumps ego.

    Han siger jo “make America great again”. Det kan man vel dårligt gøre bedre end at gøre landet bogstaveligt talt større, ved fx at få Grønland som en del af USA.

    At få Grønland giver ingen mening fra et sikkerhedsmæssigt syn. De kan allerede lave al den sikkerhed de vil. Jeg tror det handler om Trumps ønske om at huskes som den præsident der udvidede nationen mod nord.

    Jeg håber han finder ud af at han er nødt til at sluge kamelen og bare leve med ikke at få Grønland.

  • SorteKanin@feddit.dkOPtoRust@programming.dev•What does it take to ship Rust in safety-critical? | Rust Blog
    4·
    1 day ago

    An LTS release scheme, combined with encouraging libraries to maintain MSRV compatibility with LTS releases, could reduce this friction.

    This actually sounds like a good idea. Currently crates are choosing their MSRV all over the place. If we just got a bit of alignment by calling every ~17th Rust release (roughly 2 years worth of releases) an “LTS” release, then crates could be encouraged to keep their MSRV compatible with that release.

    But we also heard a consistent shape of gaps [in core]: many embedded and safety-critical projects want no_std-friendly building blocks (fixed-size collections, queues) and predictable math primitives, but do not want to rely on “just any” third-party crate at higher integrity levels.

    I think some fixed-size collections and stuff like that would be super nice in core. Something with simple, predictable semantics, just like Vec has (i.e. no optimizations for certain usage patterns, like small string optimizations and that sort of stuff). With const generics working for integers, fixed size collections in core shouldn’t even be that hard (it’s certainly been done in many crates already).

Moderates