examples
too-many-lists
examples | too-many-lists | |
---|---|---|
29 | 219 | |
3,562 | 3,027 | |
1.8% | 1.0% | |
9.4 | 0.0 | |
6 days ago | 20 days ago | |
Rust | Rust | |
Apache License 2.0 | MIT License |
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.
examples
-
What does this function signature mean?
I was taking a look at: https://github.com/actix/examples/blob/master/forms/multipart/src/main.rs
-
Authentication system using rust (actix-web) and sveltekit - File upload to AWS S3, Profile Update
Using aws-sdk-s3 requires that tokio is installed. The above code was drafted from actix forms with multipart and s3 example with few modifications. There is a Client wrapper with two main endpoints: upload and delete_file. upload uses put_object_from_file to upload files to S3 and returns the uploaded files' URLs while delete_file deletes a file. We also created some type in backend/src/types/upload.rs:
-
Workspace shenanigans
I just figured it out. I had this: https://github.com/actix/examples/blob/master/databases/postgres/Cargo.toml as my toml, and somehow I removed the actix-web.workspace = true tag, but I didn't see the derive_more one. Removed it and that fixed it.
- Trying to learn by tutorials, for cannot find a single Actix/Diesel tutorial that actually compiles
-
Trying to work with Actix-web and struggling to serve css to multiple endpoints
It doesn't need to be in another directory, creating separate folder for static content is common practice, it makes your project organization more clear and minimizes errors with overlapping and over-complicated routes/paths. Take a look at folder structure of the example project found from actix-files repository: https://github.com/actix/examples/tree/master/basics/static-files, it's great starting point where you can start extending it for your own needs.
-
How do you work with Mongo?
There's an example of using MongoDB with actix-web here: https://github.com/actix/examples/tree/master/databases/mongodb
-
How do I implement TLS/SSL/HTTPS into an actix-web application?
Sorry for the late response. Here is an example of how I implemented it using axum and rustls, and there is a similar example for actix-web here. It looks like the actix-web example follows much the same process for parsing the key and cert files and creating the rustls server config so hopefully the tls module in my example can provide some help.
- How do I use actix-web to serve yew?
-
I'm new to authentication, please help.
As of now, I can register a new user by storing a username and hashed password, and then my login page is able to insert a user's ID into my Session per this example. The problem is that when I navigate from the login page after successfully inserting a new key, the Session doesn't persist to the next page.
- SSE Actix web
too-many-lists
-
Towards memory safety with ownership checks for C
You seem to have a preset opinion, and I'm not sure you are interested in re-evaluating it. So this is not written to change your mind.
I've developed production code in C, C++, Rust, and several other languages. And while like pretty much everything, there are situations where it's not a good fit, I find that the solutions tend to be the most robust and require the least post release debugging in Rust. That's my personal experience. It's not hard data. And yes occasionally it's annoying to please the compiler, and if there were no trait constraints or borrow rules, those instances would be easier. But way more often in my experience the compiler complained because my initial solution had problems I didn't realize before. So for me, these situations have been about going from building it the way I wanted to -> compiler tells me I didn't consider an edge case -> changing the implementation and or design to account for that edge case. Also using one example, where is Rust is notoriously hard and or un-ergonomic to use, and dismissing the entire language seems premature to me. For those that insist on learning Rust by implementing a linked list there is https://rust-unofficial.github.io/too-many-lists/.
-
Command Line Rust is a great book
Advent of Code was okay until I encounterd a problem that required a graph, tree or linked list to solve, where I hit a wall. Most coding exercises are similar--those requiring arrays and hashmaps and sets are okay, but complex data structures are a PITA. (There is an online course dedicated to linked lists in Rust but I couldn't grok it either). IMO you should simply skip problems that you can't solve with your current knowledge level and move on.
-
[Media] I'm comparing writing a double-linked list in C++ vs with Rust. The Rust implementation looks substantially more complex. Is this a bad example? (URL in the caption)
I feel obligated to point to the original cannon literature: https://rust-unofficial.github.io/too-many-lists/
-
Need review on my `remove()` implementation for singly linked lists
I started learning Rust and like how the compiler is fussy about things. My plan was to implement the data structures I knew, but I got stuck at the singly linked list's remove() method. I've read the book as well, but I have no clue how to simplify this further:
-
Factor is faster than Zig
My impression from the article is that Zig provides several different hashtables and not all of them are broken in this way.
This reminds me of Aria's comment in her Rust tutorial https://rust-unofficial.github.io/too-many-lists/ about failing to kill LinkedList. One philosophy (and the one Rust chose) for a stdlib is that this is only where things should live when they're so commonly needed that essentially everybody needs them either directly or to talk about. So, HashTable is needed by so much otherwise unrelated software that qualifies, BloomFilter, while it's real useful for some people, not so much. Aria cleaned out Rust's set of standard library containers before Rust 1.0, trying to keep only those most people would need. LinkedList isn't a good general purpose data structure, but, it was too popular and Aria was not able to remove it.
Having multiple hash tables feels like a win (they're optimized for different purposes) but may cost too much in terms of the necessary testing to ensure they all hit the quality you want.
-
Was Rust Worth It?
> Cyclic references can be dealt with runtime safety checks too - like Rc and Weak.
Indeed. Starting out with code sprinkled with Rc, Weak, RefCell, etc is perfectly fine and performance will probably not be worse than in any other safe languages. And if you do this, Rust is pretty close to those languages in ease of use for what are otherwise complex topics in Rust.
A good reference for different approaches is Learn Rust With Entirely Too Many Linked Lists https://rust-unofficial.github.io/too-many-lists/
- What are some of projects to start with for a beginner in rust but experienced in programming (ex: C++, Go, python) ?
-
How to start learning a systems language
Second, once you've finished something introductory like The Book, read Learning Rust With Entirely Too Many Linked Lists. It really helped me to understand what ownership and borrowing actually mean in practical terms. If you don't mind paying for learning materials, a lot of people recommend Programming Rust, Second Edition by Blandy, Orendorff, and Tindall as either a complement, follow-up, or alternative to The Book.
- My team might work with Rust! But I need good article recommendations
-
Conversion?
Learning Rust With Entirely Too Many Linked Lists which highlights a lot of the differences with how you need to structure your code in Rust compared to other languages.
What are some alternatives?
rust-graphql-actix-juniper-diesel-example - Rust, Actix, Juniper and Diesel example project
rust - Empowering everyone to build reliable and efficient software.
poem - A full-featured and easy-to-use web framework with the Rust programming language.
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
actix-skeleton-api - An attempt to create a simple and functional API skeleton with Actix
book - The Rust Programming Language
dalted - Image processing web-app for color blindness
CppCoreGuidelines - The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++
actix-auth - A truly simple illustration of basic authorisation using actix-web and MongoDB.
easy_rust - Rust explained using easy English
actix-sse - server-sent events with actix-web
x11rb - X11 bindings for the rust programming language, similar to xcb being the X11 C bindings