banner VS nomicon

Turns out I’ve been hacking on https://github.com/rustl3rs/banner; a CI/CD system; for 3 months now. Haven’t been this into an out of work project in decades. I just keep setting really small goals, and if the animals wake me up early, I hack on that goal until it’s ready. Commit; repeat. Very happy with the progress. Some of the current progress has seen the capability to set env vars and use host directories in a task. Next step is to be able to pass the state from one task to another; at which point it will pretty much be able to dogfood itself. 🐶🦴

I'll be continuing to think and hack on Banner; my thoughts, and now code on how a CICD system should work. It has come a surprisingly long way in such a short time. It's certainly not feature complete, but it has been capable of running a test (unit-test; which could conceivably run unit-tests) for a little while. My current focus is constructing event handlers for simple cases, and allowing them to be executed when a matching event is emitted. Thinking to write the handler as a rhai script, and execute the compiled ast. But rhai isn't particularly async friendly, so may have to shift my thinking. Just started looking at Rune and it looks promising.

I’m starting to formulate some ideas I’ve had for a long time around CI/CD. No guarantees it’ll go anywhere, but I find it pretty hypocritical that we advocate for testing the skin off our code before we accept it as production ready, but then basically test in production the pipelines that deliver that automation. There just aren’t easy ways to test a pipeline before you merge it or before you make the change in production. Your pretty much forced into a practice we all dislike. Anyway, thoughts here: https://github.com/rustl3rs/banner

it’s even written by the same person that wrote the Nomicon (the guide to the dark arts of unsafe)

If you want to dive deeper you can always have other options but now there are concrete cases, if you want to do low level thing https://doc.rust-lang.org/nomicon/ while if you want multi thread/concurrency stuff https://marabos.nl/atomics/ . There are many many books so you will have to point yourself to what you want

Nonononono. SeqCst is the most error prone memory order: https://github.com/rust-lang/nomicon/issues/166

Hope this helps. For more details, see the Rustonomicon. I referenced the subtyping chapter here extensively.

Nice video! Glad I could help out. This stuff is hard, and I'm still learning a lot about it myself even years later. The Rustonomicon is a great read if you haven't already.

Have you got a moment to read through the good book , after reading through this perhaps try the Rustonomicon.

That is not what UB means. Undefined Behaviour is behaviour that the compiler is allowed to assume will never happen, and which can consequently cause miscompilations due to optimisation passes gone wrong if it does in fact occur in the source code.

It's true that Rust does not have a written specification that clearly delineates what is and isn't UB in a single place. But:

1. UB is impossible in safe code (modulo bugs in unsafe code)

2. There are resources such as the Rustinomicon (https://doc.rust-lang.org/nomicon/) that provide a detailed guide on what is and isn't allowed in unsafe code.

In practice, it's much easier to avoid UB in Rust than it is in C++.

However, this is a wide topic out of scope for a Reddit comment, so maybe just read the Rustonomicon. It explains everything about data handling in Rust.

The ownership model & borrow checker makes rust a bit of an awkward language in which to write complex data structures like trees and graphs. It can be done - since you can always use raw pointers & unsafe code when you absolutely need to to treat rust like C. But the language fights you, and the community can get a bit moralistic about this sort of thing. The rust nomicon is a fantastic resource for learning the limits of the borrow checker, and where and how to use unsafe code correctly. You will need unsafe less than you think you will, but sometimes you will have no choice.