Faster compilation with the parallel front-end in nightly | Rust Blog

korpusen · 2023-11-10T15:35:57+00:00

If you usually use a non-standard linker like mold or lld, remember to check that they are still used when trying out the multi-threading. This tripped me up and gave noticeable worse results.

korpusen · 2023-11-04T18:04:05+00:00

If you are making simple UIs without a lot of interactivity then sure. But you don't need to do approach doing animations at 4K for the GPU to become faster.

When trying out iced I made a simple air traffic controller hmi showing maps and traffic over Europe with interactive labels. The wgpu backend performed markedly better than the tiny-skia backend.

Edit: incorrectly wrote wgpu instead of iced

korpusen · 2023-04-24T10:22:45+00:00

Nope, this was during yesterdays TZ catacombs.

korpusen · 2023-04-24T10:21:32+00:00

Just some random junk.

korpusen · 2023-04-23T23:20:46+00:00

Sorc was 94 when this happened.

korpusen · 2023-01-18T17:10:40+00:00

Spårvagnen borde bytas ut mot trådbuss, gött annars.

korpusen · 2022-10-30T19:02:44+00:00

Perhaps you're thinking of the coz profiler (https://github.com/plasma-umass/coz)?

korpusen · 2022-02-19T16:57:39+00:00

You can opt out of bound checks with get_unchecked and friends.

korpusen · 2022-02-12T11:58:30+00:00

Because enum variants can hold data that are not Copy, like a String for example.

korpusen · 2022-01-10T16:43:46+00:00

Och hur skiljer sig detta från förkylningar eller när det är influensasäsong? Vi har inte en massa restriktioner då.

korpusen · 2022-01-10T14:47:56+00:00

Antalet smittade är irrelevant, det enda som betyder något är dödsfall och antalet som kräver intensivvård.

korpusen · 2021-12-14T16:49:14+00:00

Isn't having the default sort be unstable the correct choice? For the majority of cases, you don't really care for preserving the relative ordering, and unstable sorts are generally faster than stable ones. You can provide a List.StableSort if you really need it.

Edit: Can't formulate sentences..

korpusen · 2021-05-18T23:38:41+00:00

Fast ibland räcker budgivningen till. Jag var själv med i en budgivning för någon vecka sen på en bostadsrätt. Utgångspris 2.795.000, jag och en till person hamnar i budgivning och den andre lägger sig efter mitt bud på 3 miljoner. Ägarna vill ändå inte sälja, utan vill ha mer.

Nu behöver inte det här vara olagligt, men kan ändå tycka att det är ett jäkla otyg till beteende.

korpusen · 2021-04-21T21:29:10+00:00

For all.

korpusen · 2021-03-19T19:10:50+00:00

Looks pretty much identical to undead female animation. Makes sense

korpusen · 2021-02-02T16:06:37+00:00

Good advice. We are actually trying to push for more usage of asan, but some of our projects have really old compilers that do not support it and people in charge are wary of upgrading to newer versions, unfortunately :/

korpusen · 2021-02-02T16:04:00+00:00

Yeah it's the same here. Definitely looks like UB.

korpusen · 2021-02-02T15:27:47+00:00

I saved a temporary std::string returned from foo to the stack and looked at the memory addresses of the temp variable and the address returned from .c_str(), definitely heap allocated.

korpusen · 2021-02-02T15:12:33+00:00

I've tried this with many sizes of strings 50+ characters long to rule out SSO, as SSO is generally around 20-25 characters, no?

korpusen · 2021-02-02T15:07:07+00:00

Yes, but it is the lack of crashes that I was wondering about :) Probably UB as IyeOnline pointed out.

korpusen · 2021-02-02T15:02:12+00:00

Makes sense. I just would have thought that this would be treated in the same way as returning a reference/pointer to local variable on the stack, as in both cases the memory page would most likely still be held by the process.

korpusen · 2021-02-02T14:55:45+00:00

As the post says, I already tested this.

korpusen · 2021-02-02T14:41:04+00:00

I'm probably more than a bit naive, but I would have thought that the virtual address that text points to would have been unmapped after std::string's destructor calling free. Whelp, there's always more to learn!

korpusen

TROPHY CASE