lang-team
708
lang-team | 708 | |
---|---|---|
25 | 12 | |
190 | 80 | |
0.5% | - | |
7.8 | 1.8 | |
about 1 month ago | over 2 years ago | |
JavaScript | C++ | |
Apache 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.
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...
708
-
CppFront Parameter Passing Semantics
Herb's parameter passing paper describes five parameter semantics categories (in, inout, out, move, and forward) to replace C++'s parameter passing styles (value, reference, const reference, r-value reference, and forwarding reference). And it poses the question of how parameter passing semantics can reasonably be made visible at the call-site.
-
Does Rust have any design mistakes?
Another design mistake, imho, is that Rust does not have Herb Sutter’s parameter passing style from his 708 paper. For example, out parameters instantly remove almost all use-cases for MaybeUninit, adding strong compiler guarantees and requiring zero unsafe code.
-
Is C++ Doomed?
In my C++ code, I've copied Rust and expressed fallible initialization by returning a std::optional from a static method (which the article failed to mention). The problem is that (like Rust) you lose placement initialization, and (unlike C++ or Rust) you can't initialize private fields using aggregate initialization or initializer lists, and must write a passthrough constructor (which can't even be private because it breaks make_unique).
https://github.com/hsutter/708 is a C++ proposal which unifies placement constructors and writable out-parameters ("definite first use"). I don't think it makes placement initialization fallible, but I'm not sure.
-
const all the things?
As noted elsewhere - we need in/out/forward.
- Three reasons to pass std::string_view by value
-
Last reference as rvalue?
There is a proposal by Herb Sutter (708: Parameter passing -> guaranteed unified initialization and unified value-setting) that want to do just that.
-
Experience C++ developers: do you enjoy using C++ (even for personal/hobby projects?)
Having said this, I can't wait for the dream to become reality
-
Is pass-by-value slower than pass-by-rvalue-reference?
I am waiting for this to become reality, and C++ language to suddenly lose 98% of its annoyingness!
-
All C++20 core language features with examples
Oh! That would be so nice. I mean, there is a proposal in the works, but I really doubt it will be adopted as it is.
- Proposal idea : attribute to force value assignment to default-constructible member in constructor
What are some alternatives?
Idris2 - A purely functional programming language with first class types
dyno - Runtime polymorphism done right
rfcs - RFCs for changes to Rust
mold - Mold: A Modern Linker 🦠
diamond-types - The world's fastest CRDT. WIP.
rust - Empowering everyone to build reliable and efficient software.
isahc - The practical HTTP client that is fun to use.
semver-trick - How to avoid complicated coordinated upgrades
STL - MSVC's implementation of the C++ Standard Library.
rustc-dev-guide - A guide to how rustc works and how to contribute to it.
rfcs - RFCs for changes to Rust