Firestar99

It seems to be a UI-only bug, as saving and reloading the capture fixes the labeling

Finally had some time to take a look and I have no idea why it didn't work in the first place. Specifying the profiling features on the binary crate is...

I've turned this PR into a draft, as I've added `DescriptorSet::invalidate()` to it and ~~haven't gotten around to extensively test it~~ tested it and it works :D

> So any record-time checks on the bound resources are probably superfluous? Yes they are, so for now I've just disabled them. Which means they are indeed not validated at...

~~I'm seeing some weird performance behavior in bistro I would like to investigate first before officially submitting this~~ Resolved: attached RenderDoc hates super large cmd buffers of 3000+ draws.

I'm uncertain how secondary cmd buffers are handled. I could imagine a usecase, when they contain many draws with always changing pipelines (which is generally frowned upon anyways) and with...

> And you could rename the gcore::raster module to something else to avoid coflicts. Then we don't have to rename anything in editor This PR makes `editor` to only depend...

The linker is erroring due to the wasm-specific flags somehow ending up in a native compile, probably env leaking again. Doesn't trigger locally, likely due to me using the mold...

Superseded by https://github.com/GraphiteEditor/Graphite/pull/3097 and https://github.com/GraphiteEditor/Graphite/pull/2985

> why the Backtrace is wrapped in an Arc I don't have the time right now to investigate that further, feel free to do that yourself or leave the PR...