cargo-leptos
include-what-you-use
cargo-leptos | include-what-you-use | |
---|---|---|
4 | 39 | |
311 | 3,893 | |
4.5% | 3.1% | |
8.8 | 9.4 | |
3 days ago | 7 days ago | |
Rust | C++ | |
MIT License | GNU General Public License v3.0 or later |
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.
cargo-leptos
-
I Improved My Rust Compile Times by 75%
> separate-front-target-dir = true
This is now enabled unconditionally and the Cargo.toml option is deprecated since cargo-leptos 0.2.3, it is going to be removed in 0.3
https://github.com/leptos-rs/cargo-leptos/pull/216
https://github.com/leptos-rs/cargo-leptos/issues/217
https://github.com/leptos-rs/cargo-leptos/commit/b0c19a87cff...
-
Hey Rustaceans! Got a question? Ask here (16/2023)!
Leptos is a SolidJS-like framework with excellent performance. It has a great server-side story as well with server-side rendering & client-side hydration as well as what they call "server functions"; essentially define a function server-side and it can be called client-side without having to deal with http and API design. Also great tooling story with cargo-leptos, leptosfmt (as well as leptos-language-server)
-
What are some stuff that Rust isn't good at?
Leptos got it working a couple weeks ago as well: https://github.com/leptos-rs/cargo-leptos
-
Yew | What’s been your experience?
Future opportunities - This one's tougher to speak to since leptos is new on the block. I think it's worth exploring leptos (or sycamore?) just to learn about fine-grained reactivity, and comparing how it works compared to a traditional react model. But to me the ecosystem around leptos is promising, with tools like cargo-letpos, leptosfmt, and more, it seems the community is stepping up to help fill some gaps.
include-what-you-use
- IWYU: A tool for use with Clang to analyze includes in C and C++ source files
-
Script to find missing std includes in C++ headers
Interesting...how does it compare to https://github.com/include-what-you-use/include-what-you-use ?
-
Speed Up C++ Compilation
Build Insights in Visual Studio, include-what-you-use).
Looks like https://include-what-you-use.org/ might do that.
-
Is it good or bad practice to include headers that are indirectly included from other headers?
If you are worried about includes, use https://github.com/include-what-you-use/include-what-you-use and stop thinking about it.
-
how do you guys manage a include file mess ?
Getting rid of that is not straightforard, though some tools can help with that
-
Is it appropiate to comment what a header is needed for?
You can use the tool https://github.com/include-what-you-use/include-what-you-use to do this for for. It tracks included files and can give comment for what is used from each file. It also warns you when you include files that you don’t use
-
Hey Rustaceans! Got a question? Ask here (16/2023)!
Invisible imports (e.g. traits). In Python, everything is fully namespaced (unless you from import * in which case all bets are off). It's always explicit where a name is coming from. C is the opposite: #include lets you refer to anything defined in the headers with no namespacing. That's why a common strategy (include what you use) has an associated code style: after every non-std #include you have a comment saying which of its definitions you are using. Of course, Rust is much less implicit, but I still sometimes struggle with traits. For example, you can use tokio::net::TcpStream, but you need to also use tokio::io::AsyncReadExt for the .read trait to be defined on TcpStream. This makes it hard (for me) to answer questions like "what traits are currently available in this scope?" and "why is this module being imported?"
- I implemented a NASA image compression algorithm
-
IncludeGuardian - improve build times by removing expensive includes
Aside from being closed source and not available on all architectures, how does it compare to iwyu(https://include-what-you-use.org/) or clang's relatively recent include-fixer which is also accessible via clangd?
-
Do you include standard library headers in your implementation file, if they're already been included in the corresponding header file?
I set up include-what-you-use and I let it tell me which headers should be where. The IWYU rules would have put all needed headers including in the cpp file.
What are some alternatives?
leptos - Build fast web applications with Rust.
cppinclude - Tool for analyzing includes in C++
dioxus - Fullstack GUI library for web, desktop, mobile, and more.
coc-clangd - clangd extension for coc.nvim
IRust - Cross Platform Rust Repl
cpplint - Static code checker for C++
rusty-css - a solution to create and export css styles in a familiar way, but without leaving the rust syntax. You can access and manipulate every value you define on an individual basis.
clangd - clangd language server
rfcs - RFCs for changes to Rust
Cppcheck - static analysis of C/C++ code
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
uncrustify - Code beautifier