tool-conventions
lang-team
tool-conventions | lang-team | |
---|---|---|
3 | 25 | |
287 | 191 | |
2.4% | 1.0% | |
5.6 | 7.8 | |
10 days ago | about 1 month ago | |
JavaScript | ||
Artistic License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tool-conventions
-
Isolates, MicroVMs, and WebAssembly (In 2022)
> Better interoperability
AFAIK, the examples you give all target a basic C ABI [0] or can be made to target the same ABI. In Rust, it means targeting wasm32-unknown-emscripten
The Rust team is also working on a "WASM ABI"[1] which would be useful in taking advantage of stuff like multi-value returns, and other compilers could just choose to target that. More likely, the C ABI on WASM will be updated to account for missing features, and that'll be the standard for interoperability in the WASM ecosystem.
[0]: https://github.com/WebAssembly/tool-conventions/blob/main/Ba...
[1]: https://github.com/rust-lang/lang-team/blob/master/design-me...
-
Features of a dream programming language: 2nd draft.
C ABI: Compatible with the C language Application Binary Interface (ABI). So code in the language is usable from other languages. Inspired by Zig. Since compiling to WASM is desirable, WASM's C ABI could probably be used, instead of a separate implementation towards the C ABI.
-
Crates for (mutable) statics with non const initialization.
There is maybe a solution. From what I found the linker will glue constructor functions and they have an associated priority. (look https://github.com/WebAssembly/tool-conventions/blob/master/Linking.md here for the "linking meta data section"). I explored the ldd/wasm source code directory and it looks like there are also destructor functions. I have not found out in which sections such functions should be placed (after 1h of exploration). Would you like to pursue? I am ok to receive pushes or even share owner ship of the repository.
lang-team
-
Totally_safe_transmute, Line-by-Line
The Rust team did a deep dive on the bug in 2020, which has some more details that might be helpful to understanding what's going on: https://github.com/rust-lang/lang-team/blob/master/design-me....
-
Using enums to represent state in Rust
I haven't been following this closely, so I looked it up and it looks like that's not going to happen for the foreseeable future unfortunately:
https://github.com/rust-lang/lang-team/issues/122
Kind of a shame, but wrapper types work well enough that I understand. It does look like if there was someone with enough resources to make it happen that they'd be receptive to it.
- Should Error enums be `non_exhaustive`?
-
What features would you like to see in rust?
Did you read the link the original comment posted? I think that explains the idea rather well https://github.com/rust-lang/lang-team/issues/122
-
Pattern matching tuple variant of enum without deconstructing tuple
A quick search pulled up this as a likely candidate for most recent discussion of it but it goes back at least to 2016 with this RFC.
-
State Machines III: Type States
There have been at least one proposal and RFC in the past that seem to be deferred or closed due to bandwidth issues.
-
The type system is a programmer's best friend
That's what Rust does, and it's considered a problem (that the devs are regrettably unable to reasonably solve) rather than a good thing.
-
In-line crates
Lang had some conversations about this: https://github.com/rust-lang/lang-team/issues/139
-
LKML: Linus Torvalds: Re: [PATCH v9 12/27] rust: add `kernel` crate
The design of Rust panics unconditionally aborts the program if you panic while unwinding, and some people even want to abort if you panic in Drop.
-
Isolates, MicroVMs, and WebAssembly (In 2022)
> Better interoperability
AFAIK, the examples you give all target a basic C ABI [0] or can be made to target the same ABI. In Rust, it means targeting wasm32-unknown-emscripten
The Rust team is also working on a "WASM ABI"[1] which would be useful in taking advantage of stuff like multi-value returns, and other compilers could just choose to target that. More likely, the C ABI on WASM will be updated to account for missing features, and that'll be the standard for interoperability in the WASM ecosystem.
[0]: https://github.com/WebAssembly/tool-conventions/blob/main/Ba...
[1]: https://github.com/rust-lang/lang-team/blob/master/design-me...
What are some alternatives?
ts-belt - 🔧 Fast, modern, and practical utility library for FP in TypeScript.
Idris2 - A purely functional programming language with first class types
dwarf-2-sourcemap - A DWARF to SourceMaps converter for WASM
rfcs - RFCs for changes to Rust
wyrcan
diamond-types - The world's fastest CRDT. WIP.
ramda - :ram: Practical functional Javascript
isahc - The practical HTTP client that is fun to use.
krustlet - Kubernetes Rust Kubelet [Moved to: https://github.com/krustlet/krustlet]
semver-trick - How to avoid complicated coordinated upgrades
io-ts - Runtime type system for IO decoding/encoding
rustc-dev-guide - A guide to how rustc works and how to contribute to it.