When your language doesn't ship with the functionality that enables that language's core use case, this is the only outcome that can be expected.https://twitter.com/BnJ25/status/1259386240908046336 …
-
Show this thread
-
Replying to @Lucretiel
Am I naive in thinking we might be in a position, 6 months or so from now, to start upstreaming some of the more controversial trait into std thus resolving (or easing) the cross-runtime compatibility pains?
2 replies 0 retweets 3 likes -
Replying to @algo_luca
I think the bigger issue is that a cross-runtime *interface* needs to be discovered. Right now all the runtimes I'm aware of provide their functionality through globals, which means that any library that uses a runtime has to depend on it directly, rather than using an interface
1 reply 0 retweets 0 likes -
Replying to @Lucretiel @algo_luca
Most of the proposals I'm aware of involve a global attribute that installs the runtime, similar to how allocator swapping works, and then provides an stdlib interface that uses the installed runtime (or panics if none exists)
1 reply 0 retweets 1 like
This is as well the latest line of proposal I have seen in the wild.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Writing about stuff to learn how it works, mostly in Rust.
Lead Engineer at