207 private links
When you live by the C,
juggling pointers, like razor blades,
while memory bleeds,
and comprehension fades,
you know what you need -
implement it, you must!
All your codebase
are turn to Rust!
- parse a phone number
- normalize a phone number to E164 from local phone number or international codes
- detect if the phone number is valid
- get the country code from a phone number
Called "impl Trait type"
an arena is a way to store your data somewhere without directly going through the system allocator. If you have a lot of small objects which you don’t mind to deallocate together instead of individually, this can be a lot faster. You could use a Vec for this. However, if you store data in a vec its address might change all the time.
First, you need to describe the intent of your code and give an overview of how it works both at a macro level (in the README / wiki) and at the micro level, by commenting functions, structures and packages. Document, document, document.
Second, give examples on how to use your code. Snippets that users can quickly copy/paste and "feel it". Even better, add comments with the expected output to your examples.
Three, write simple code.
the goal for rainfrog is to provide a lightweight, terminal-based alternative to pgadmin/dbeaver.
An experiment to build a web browser based on Servo.
EDIT 2024-12-30: it has tabs now https://social.tchncs.de/@Blort/113740179696427117
The "(no)alloc" next to "(no)std" is a feature to disable the heap, and enforce only static allocation.
For a long time (and having a history in embedded) I think: Stack is enough if you have understood what you are about to write and are able to make design decisions aka good software.
I know half of them, and happy to discover the other half:
Jeremy Chone
Lets Get Rusty
Jon Gjengset
The Rusty Bits
Code to the Moon
Brooks Builds
No boilerplate
Logan smith
Chris biscardi
Tim clicks
Dario
sphaerophoria
Francesco Ciulla
The official website can be found on https://www.cedarpolicy.com/en
Cedar is a language for defining permissions as policies, which describe who should have access to what. It is also a specification for evaluating those policies. Use Cedar policies to control what each user of your application is permitted to do and what resources they may access.
One keylearning: write functions
- Memory safety (while working in the aerospace industry with an emphasis on space). Then the rest.
- welcoming community
- good documentation & tooling
- fun to write (in a way??)
- good compiler errors
- fast && secure
- queer community (feel like the Rust community is extra gay 💖)
- great for CLI tools
- the different approach for working with memory (borrow-checker).
- correctness
- fast & small executables
- quality of learning tools
- AI support through a critical mass of resources
- easy once the learning cliff is reached, compared to never-ending list of weird special cases in other languages
- consistent language
- everything is an expression
- pattern matching and enum variants
cargo doc --open -p <crate>
This opens documentation in the web browser for any crate that a project might be using.