←back to thread

Show HN: Unbug – Rust macros for programmatically invoking breakpoints

(github.com)
88 points BrainBacon | 9 comments | 20 Nov 24 13:33 UTC | HN request time: 0.001s | source | bottom

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 #
1. dvtkrlbs ◴[20 Nov 24 14:05 UTC] No.42194026[source]▶
You can pin versions with the rust-toolchain.toml file you need to be using Rustup afaik. Nightly is just the daily builds.
replies(2): >>42194058 #>>42197476 #
2. johnisgood ◴[20 Nov 24 14:11 UTC] No.42194058[source]▶
I assume any "nightly" version would work in this context, meaning it would not refer to a version from a year ago, as it would have already been made stable by that point, right?
replies(2): >>42194082 #>>42194127 #
3. traxys ◴[20 Nov 24 14:14 UTC] No.42194082[source]▶
"nightly" versions also allow to use unstable features, and unstable features may remain so for a very long time (potentially forever) without breaking, so an old nightly could maybe work
replies(1): >>42194218 #
4. monocasa ◴[20 Nov 24 14:20 UTC] No.42194127[source]▶
A lot of people pin a specific nightly since the feature they're depending on could change (or ostensibly it would be in stable), so they can keep working without continuously having to track nightly changes or deal with it breaking on a different system with a different nightly version.

That obviously only works for non-library uses of nightly.

5. johnisgood ◴[20 Nov 24 14:33 UTC] No.42194218{3}[source]▶
Right, not everything gets merged to stable. In that case: letting us know the specifics beyond "nightly" is advisable, IMO.
replies(1): >>42194533 #
6. do_not_redeem ◴[20 Nov 24 15:08 UTC] No.42194533{4}[source]▶
The readme does mention the specifics, immediately after mentioning nightly.

> BREAKPOINTS REQUIRE ENABLING THE EXPERIMENTAL core_intrinsics FEATURE

replies(1): >>42194632 #
7. johnisgood ◴[20 Nov 24 15:20 UTC] No.42194632{5}[source]▶
How do I know which versions of nightly support that feature, and that specific version of the feature though?

I like your username.

replies(1): >>42195593 #
8. GolDDranks ◴[20 Nov 24 16:34 UTC] No.42195593{6}[source]▶
Just use a recent nightly and you should be fine. Rust project doesn't offically provide support even for old stable versions, so "using nightly" with no specifics generally means using any nightly build, around or newer than, the current stable release.
9. kookamamie ◴[20 Nov 24 19:53 UTC] No.42197476[source]▶
I thought nightly is for nightly builds. I'll get my coat.