CEO bonuses should be awarded 10 years after their mandate
CEO bonuses should be awarded 10 years after their mandate
Would it makes sense to provide a “share nothing” runtime implementation that can be injected at startup?
Isn’t this tokio::task::spawn_local
?
It also seems to require a GC though…
newxml is GC only, for simplicity sake.
Pointers are not guaranteed to be safe
So I guess they are forbidden in @safe
mode?
but it’s being replaced by something else instead
Do you know what is the replacement? I tried looking up DIP1000 but it only says “superceded” without mentioning by what.
This makes me wonder how ready D is for someone that wants to extensively use @safe
though.
For local variables, one should use pointers, otherwise
ref
does references that are guaranteed to be valid to their lifetime, and thus have said limitations.
Should I take this to mean that pointers instead are not guaranteed to be valid, and thus are not memory safe?
Note that Rust does not “solve” memory management for you, it just checks whether yours is memory safe. Initially you might rely on the borrow checker for those checks, but as you become more and more used to Rust you’ll start to anticipate it and write code that already safisfies it. So ultimately you’ll still learn how to safely deal with memory management, just in a different way.
Rust for Linux used to be developed in parallel to the mainline Linux before Linus Torvalds merged support in the main tree.
“safe by default” can be done by starting your files with
@safe:
Last time I heard about that it was much more limited than Rust, for example it even disallowed taking references to local variables. Has something changed since then?
But the one time I looked at a rust git repo I couldn’t even find where the code to do a thing was.
IMO that tells more about how the project was organized and names things than the language used.
So I think probably, the best way IS to go the way linus did. Just go ahead and write a very basic working kernel in rust. If the project is popular it will gain momentum.
As the other commenter pointed out, there’s Redox. The issue is that this completly disregards an incremental approach: you have to rewrite everything before it comes usable, you can’t do it piece by piece. Currently the approach of Rust for Linux is not even to rewrite things, but to allow writing new drivers in Rust.
Trying to slowly adapt parts of the kernel to rust and then complain when long term C developers don’t want to learn a new language in order to help isn’t going to make many friends on that team.
Have you seen the conference video? That’s not just refusal to learn a new language, it’s open hostility. And it’s not the only instance, for example Asahi Lina also reported unreasonable behaviour by some maintainers just because she wrote Rust code, even when Rust was not involved.
The reputation loss is probably worse than whatever fine they end up paying
Time to pull a Meta/X and change name
Unfortunately some things will IMO always remain a natural monopoly. For example good luck trying to convince developers to write their apps for all those different operating systems.
That doesn’t really excuse its behavior in the video though.
Luckily Apple strictly controls the App Store and will never allow apps to abuse this, right? Right?
Your parent comment was mentioning the fact that their store still does not support user reviews, which should be one of the most basic features.
compile rust 0.7 in scala
Not sure if there was another rewrite, but AFAIK (and the article agrees with me) rustc was originally written in Ocaml
Epic chose not to try and compete with Steam on that front
Forget competing, they lack even the basics.
Have you actually measured a performance impact from RefCell
checks?
Where’s the punch?
In the face of everyone expecting an upgrade
Gnome 47 will have support for accent colors if that’s what you want.
No, macros can see only the tokens you give them. They have no notion of the fact that
crate::functions
is a module, thatPluginFunction
is a trait and thatfunctions_map
is a variable. Not even the compiler may know those informations when the macro is expanded.If you really really want to do this, you can use something like
inventory
. Note thatinventory
uses a special linker section to do this, which some consider a hack. This is also not supported on WASM if you want to target it.