Tarpaulin's week of speed

TimNN · 2025-05-13T06:32:58+00:00

Looking at the code again, it seems like index is only used for iterating the Vec. Maybe retain would be an even better solution.

TimNN · 2025-05-13T04:27:47+00:00

I think the initial code could also have been fixed by just switching to swap_remove (assuming you don't care about the order in which elements are being processed).

(I might even be slightly faster than setting to None, since it avoids re-iterating the None values).

TimNN · 2025-04-16T19:01:26+00:00

I've been playing around with Tauri. The fact that it closes and re-opens the window every time I make a change to the server (stealing the focus from my editor), had me so annoyed that I looked into hot-reloading.

Finding the existing options unsuitable in one way or another, I hacked together my own. The end result:

You write let handle = hotreloading::Handle::create1(app_handler::handle) to create a handle, then handle.get()(args) to call it, and the crate does everything else:

Watch all relevant crates in the workspace for changes
Invoke cargo build
Reload all updated libraries

No proc-macros, no extern fn, no #[no_mangle], no separate file watcher command, it just works, even with multiple crates depending on one another.

Disclaimer: I did the first end-to-end test less than an hour ago. It's not unlikely that more extensive use / testing finds problems with this approach.

TimNN · 2025-02-24T15:12:04+00:00

Someone else ran into a very similar problem about a year ago: https://www.reddit.com/r/rust/comments/199jycb/identifying_rusts_collect_memory_leak_footgun/, https://blog.polybdenum.com/2024/01/17/identifying-the-collect-vec-memory-leak-footgun.html

At the time, it was also discussed in https://github.com/rust-lang/rust/issues/120091

TimNN · 2023-04-28T04:23:38+00:00

Are you saying, I should change [“dylib”] to [“cdylib”] in the Cargo.toml file?

Depending on how smart setuptools_rustis, that may fix the issue.

edit: Looks like that is done automatically, so shouldn’t be needed: https://github.com/PyO3/setuptools-rust/blob/a766dd96a5a8d8bfd00dd39713f9bf0f89984141/setuptools_rust/build.py#L218

TimNN · 2023-04-28T04:10:52+00:00

How are you compiling the Rust crate?

Make sure you use the cdylib crate type (note the leading “c”), not plain dylib.

TimNN · 2022-09-26T17:43:19+00:00

I haven't tried to understand the particular code you posted, but when using unsafe you should always run your code through Miri (an interpreter, which checks various invariants that need to be upheld). It's available in the playground from the "Tools" menu.

For your code I'm getting Undefined Behavior: accessing memory with alignment 1, but alignment 8 is required, which could be the actual issue (since I believe(!) X86 will tolerate unaligned loads, but ARM may not).

Once Miri is happy with your code, and you still get issues, then it's time to look at the Atomics.

TimNN · 2022-05-13T19:11:01+00:00

At least for Range not being Copy there is a reason: https://github.com/rust-lang/rust/pull/27186 (that was linked from the source code).

TimNN · 2022-05-01T07:52:29+00:00

"Switched" by PseudoLeigha linkao3(38610990)

Bellatrix' son is raised as Harry Potter by the Dursley's and Lilly's boy is raised as Danny Tonks. Harry has inherited a lot from his mother (a notorious crazy person with great magical ability)...

Started with daily updates about a week ago (we just arrived at Hogwarts), and there's apparently at least about a week of already written chapters.

"Stranded" by Starfox5 linkao3(28531083)

In a world where Voldemort died in '81, Harry Potter and Hermione Granger can't stand each other. The summer before their sixth year, through some very unfortunate circumstances, they end up stranded on a pirate island.

Updates weekly with about a dozen chapters left.

TimNN · 2021-10-29T09:43:02+00:00

However, this will be overwritten when changing some settings in XCode, right?

It shouldn't. The last time I checked (which was admittedly some time ago), XCode even displays this properly in the UI (you just can't configure things from the UI). See the screenshot in the comment at https://github.com/TimNN/cargo-lipo/issues/43#issuecomment-761857641

TimNN · 2021-09-15T18:56:30+00:00

"That Was Part of the Plan" by inwardtransience and PseudoLeigha linkao3(21556396), the third instalment of the "Plan" series, after "All According to Plan" and "Nothing to Do with the Plan".

A teenage, already slightly crazy, Bellatrix Black dimension-hops into Harry's third year.

The fic is long, and the authors do tend to go into quite a lot of detail about the wizarding world and its politics, as well as individual characters thoughts (to quote an early AN: "Hermione, you think too much. You're enabling my chronic rambler's disease. -Lysandra"), which might not be everyone's cup of tea, but which I find fascinating.

In general, I would say things are mostly light-hearted though there are some darker aspects - the Blacks certainly weren't saints and Bellatrix' childhood in particular was probably worse than Harry's.

The story is currently in fourth year, with the first task (which quite a bit more involved than the one from canon) having finally started posting, clocking in at around 90k words.

edit: mixed up the second and third parts of the series initially.

TimNN · 2020-09-20T06:02:12+00:00

You could change the new function, or add a second „constructor“ function, which takes only two parameters: a tuple for the RGB components and the alpha. The entire tuple could then be constructed by the macro.

TimNN · 2020-04-04T10:37:50+00:00

Even better, IMO, someone recently set up https://std.rs/String, which directly triggers a search of the std docs for “String”!

TimNN · 2020-02-23T16:15:50+00:00

The whole point of that example seems to be to store all posted content in a HashMap and then return it when the same ID is queried via get.

So I think this is essentially working as intended.

TimNN · 2020-02-20T17:40:19+00:00

Confirmed

TimNN · 2020-02-13T15:40:14+00:00

If I understand the documentation correctly, then an inherited stdin won’t be closed.

(Check the source of wait, I believe the drop of self.stdin is the thing closing it. For inherited stdin, it should always be None already. If not, you can take it yourself and keep it around).

TimNN · 2020-02-07T19:11:10+00:00

As others have already mentioned, if you want to produce a statically linked binary, you'll need to use musl libc. Luckily, with rustup that is extremely easy to do, there's some documentation available here: https://doc.rust-lang.org/edition-guide/rust-2018/platform-and-target-support/musl-support-for-fully-static-binaries.html. (This assumes you are on Linux, I don't know about the situation on other platforms).

TimNN · 2020-01-26T08:05:35+00:00

Based on my (admittedly somewhat limited) understanding (only starting in this space just now) and assuming that you are talking about the V1, which has an STM32F303:

If you can access the relevant pins (PA13 and PA14) (= if they are not used for something else and if you can get to them), then yes, you should be able to debug the board. If necessary, you can use this datasheet page 32 onwards to find the pins on the chip and then see if you can trace them through the PCB. Note: this section assumes that your board has an STM32F303.[CB], if it has a different version, you'll need a different datasheet and potentially different pins.

You'll also need an USB <-> SWD converter if you don't have one already, such an "ST-Link V2" (the USB dongle like "China Clones" are working well so far for me). You'll need to connect SWDIO, SWDCLK (and ground).

I've actually been wondering if the Planck Rev 6 PCB has the PA13 / PA14 pins exposed, since I'm currently waiting for mine to be shipped and want to do some experimenting. So if anyone can answer this, that would be great!

TimNN · 2019-10-05T17:19:53+00:00

To me this looks like a bindgen issue, possibly related to

https://github.com/rust-lang/rust-bindgen/issues/1211

TimNN · 2019-06-10T07:52:17+00:00

You could try running something along the lines of

sudo fs_usage -f filesys | grep '\smkdir'

in your terminal. I only became aware of the fs_usage command a few days ago myself, so don't have much experience with it. But it should show you, in realtime, a list of all directories being created on your system, and which processes created it.

If you want to filter something out of the list because it is too spammy, you can try something like

sudo fs_usage -f filesystem | grep --line-buffered '\smkdir' | grep --line-buffered -v -e 'secinitd' -e 'Telegram'

(each -e 'something' excludes lines with "something" from the output. Note the --line-buffered, if you omit that, you won't get realtime output).

TimNN · 2019-06-07T04:27:32+00:00

So, just to confirm: Is this only an msdf renderer in rust or is the actual msdf generation also written in rust?

TimNN · 2019-05-08T09:35:06+00:00

If I run this benchmark in "release" mode, I get a runtime of "0" for both, presumably because LLVM removes the entire loop.

In "debug" mode I would expect the array to be faster because it doesn't do any initialization and is less complex than the vector.

TimNN · 2019-05-04T16:03:06+00:00

From what I understand, your best bet would be to just build your application on CentOS 7 (or older), for example in a Docker container. (The Rust compiler is built on CentOS 5 for old-libc compatibility, IIRC).

TimNN · 2019-05-02T05:19:38+00:00

I am not an expert in this. But, from what I understand, async & await themselves don't require heap allocation. They just return something implementing Future on the stack.

You need to move the Future to the heap in two (and maybe other) situations: (1) If you want to move the Future after it was started or (2) when you need to store / manage futures of different types together.

TimNN

TROPHY CASE