-
-
adventofcode
Advent of Code solutions of 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022 and 2023 in Scala (by sim642)
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
Windows Terminal
The new Windows Terminal and the original Windows console host, all in the same place!
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
-
-
Have you seen the book Rust Design Patterns?
I don't need anything complex, I'm just getting some things ready for Advent of Code this year, and want to be able to create a new crate for each day that has some basic structure setup.
Is there way to create a new crate from a template using cargo I've found cargo-create, but it fails to install and all the repositories/documentation 404. I've also seen an RFC to add it directly to cargo, but it looks like it's postponed.
Take a look at cargo-generate.
It's not a general purpose template crate initializer, but I've written a tool specifically for AoC initialization: https://github.com/coriolinus/aoctool
Personally I've never understood this desire. Sure, I like Rust a lot, but when I'm using an application I don't really care what language(s) it is written in, so long as it does its job well and efficiently. I usually use the new Windows Terminal which is actually not half-bad, though I often use the integrated terminal inside VS Code as well.
There's a few ways to do it. The low-level method is to write a HLSL shader then use something like vulkan to run it (vulkano example). If you want a 100% rust method, then wgpu and rust-gpu exists to let you define your shaders directly in rust while they handle more of the boilerplate.
There's a few ways to do it. The low-level method is to write a HLSL shader then use something like vulkan to run it (vulkano example). If you want a 100% rust method, then wgpu and rust-gpu exists to let you define your shaders directly in rust while they handle more of the boilerplate.
I hope this is an easy question, so: what's the best path for integrating something like chafa into a rust project?
What's the goal with creating linux executable? If it's for distribution, I think github actions are good. If it needs to be run on another machine during the dev cycle, a --target is probably best. If it's just for testing different configurations or because you use a library that doesn't work on mac, then cross/docker are good.
if you wanna do it the "right" way, I'd say to make a chafa-sys crate using something like bindgen, then create a wrapper over chafa-sys using idiomatic rust. If you just want a quick access to a few methods, then libc + extern blocks aren't too bad.
Yea, 90% of stuff can be compiled using --target and distributed by just copying it. The notable counter example I've run into ring. It's relied on by rusttls, which is the backbone of a lot of webservers.
There are some Rust ORMs that map nullable fields to options. Then there are novel databases written in Rust such as https://github.com/mit-pdos/noria