←back to thread

Show HN: Unbug – Rust macros for programmatically invoking breakpoints

(github.com)
96 points BrainBacon | 1 comments | 20 Nov 24 13:33 UTC | HN request time: 0.21s | source

This project is inspired by some of the asserts in Unreal engine.

Due to reliance on core_intrinsics it is necessary to develop using nightly Rust, but there are stubs in place so a production build will not require nightly.

I recently released version 0.2 which includes no_std support and adds optional log message arguments to the ensure macro.

Show context
revskill ◴[20 Nov 24 13:49 UTC] No.42193918[source]▶
What does nightly mean ? I hate that you could not know a specific version of a nightly.
replies(3): >>42193965 #>>42194026 #>>42197811 #
nindalf ◴[20 Nov 24 13:57 UTC] No.42193965[source]▶
The master branch of the Rust repo is built every night and distributed. That's a nightly build. Most people are on the stable release, which is updated every six weeks.

A minority use the nightly build for various reasons: a feature that hasn't reached stable yet, or because they want to help test the nightly releases and prevent bugs from reaching stable.

replies(1): >>42194032 #
jtrueb ◴[20 Nov 24 14:06 UTC] No.42194032[source]▶
Is it a minority? Are there stats posted for this?

Only recently have I had some projects switching to stable after their required features stabilized.

replies(2): >>42194079 #>>42197108 #
1. littlestymaar ◴[20 Nov 24 19:08 UTC] No.42197108[source]▶
> Only recently have I had some projects switching to stable after their required features stabilized.

While this used to be very common back then (in 2016-18 many things where progressively stabilized and you had cornerstone libraries switching to stable at almost every release) it hasn't been so for the past 5 years.

Rust gets way less “exciting” new features nowadays, as the language has settled a lot (there are still moving parts, but they are the minority not the norm).