Elias Gabriel Amaral da Silva

Maybe publish 0.1.2 to crates.io with the [r# fix](https://github.com/estebank/makeit/commit/5fb4e5731f2c97703c1931fe30cf31a789e519ed)? It appears the published 0.1.1 version [doesn't have it](https://docs.rs/makeit-derive/0.1.1/src/makeit_derive/lib.rs.html#9)

> Some context,this tool wasn't written for linux, it was written for Fuchsia which has a very different set of constraints. This is called out in the first line of...

It seems to me that deprecation is relatively uncontroversial but removal may not be. The only thing this RFC has to say about it is: > Deprecation without removal could...

@jhpratt it's still useful to communicate clearly when and if something deprecated is expected to be removed, rather than let the users guess. And here I say "if" because some...

> they do, if you use curly braces (except for tuples): > https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=b95fe39281037ac567cfc8dfa7aba44b Wait, so `T { 0: 5 }` works but `T(5)` doesn't? This sounds like a bug.

But rustversion can enable/disable an arbitrary amount of code, right? So, what about this? ```rust #[rustversion::nightly] #![feature(unboxed_closures)] ```

Here's an idea: add the required #![feature] using a build script. For all other things, use rustversion. That's hacky but at least you don't have to use a stable feature...

Actually, in this case.. it's much better to enable the `stable` feature flag in the build script, with [this](https://doc.rust-lang.org/rustc/command-line-arguments.html#option-cfg), and people that depend on leptos won't have to set this...

Hello, is there plans for rebranding? If this project is going forward, it's better to do a hardfork and adopt a new name. (unless Github makes https://github.com/atom-archive/xray a redirect to...

@MierenManz did it increase the compile time for non-lite builds? I think having a longer compile time is a reasonable tradeoff if you want to ship the smallest binary possible.