Rémy Rakić

It's actually pronounced @[email protected]

[Rémy Rakić @lqd]

@mitchellh So currently, the longer, more difficult projects (parallelism, codegen backend, linker, etc) are still in-progress. That compounds negatively with the lack of funding, so the volunteers driving the work also don't have a lot of time available to make progress.

[Rémy Rakić @lqd]

@mitchellh It is taken seriously but progress on improving compile times has slowed down recently: the easy low-hanging fruit, which drove most of the gains in the last few years, has been picked already.

[Rémy Rakić @lqd]

@compiler_errors much thanks for noticing my silly `TypeRelation`s mistakes <3

[Rémy Rakić @lqd]

It seems that the (slow, buggy) eagle has landed.

[Rémy Rakić @lqd]

@pcwalton alternatively, and something you can do today with plenty of disk space: setup r-a to use another output folder so there's nothing to block on while building either

[Rémy Rakić @lqd]

@gcouprie @fulmicoton clairement, et avec de l'expérience aussi, qui d'autre aurait autant de ... gestion d'erreur ?!

[Rémy Rakić @lqd]

@burntsushi5 @ibraheemdev https://t.co/UN0ToXawIi also has cool papers on this topic, as well as rust implementations (that they claim are SoTA) and benchmarks, e.g. https://t.co/GUp5FcUuAu

[Rémy Rakić @lqd]

@withoutboats I don't know if you saw this, but https://t.co/nEv8EZMQUs was another recent example where a Drop impl and destructuring interfered, """causing""" a leak during a refactoring.

[Rémy Rakić @lqd]

@djco If you're using apple's latest linker then it shouldn't matter to you IIUC: it's already competitive/better than lld/mold already. For ld64, it's debatable.

(Some targets w/ rust-lld by default: https://t.co/bV3RZAXjUM)

On linux, compared to GNU ld/bfd, the speedup is massive.

[Rémy Rakić @lqd]

If you care about rust compile times, this may be of interest: we've recently switched rustc to use lld on x64 linux (on nightly only for now to expand testing, before enabling it on stable).

I wrote more about it, with details and perf improvements, in https://t.co/zzKWO9laZL

[Rémy Rakić @lqd]

@algo_luca Let's pour drinks in honor of japaric and bstrie

[Rémy Rakić @lqd]

@algo_luca @fasterthanlime And now neither can I

[Rémy Rakić @lqd]

@thorstenball btw have you also seen Raph Levien's "Rope Science" series of posts? https://t.co/QIQQL9j045

[Rémy Rakić @lqd]

@thorstenball why the inlay hints are cool: the parameter name hint on `join_all` looks to be `iter`, so you may not even need to collect your tasks in a vec before hand🤔

[Rémy Rakić @lqd]

@nomad421 I guess you could similarly also `read_until` 0xA into your own Vec of u8s.
Is it common in line-processing tasks that the bottleneck is in checking utf8 validity rather than the task itself? If so, you could ask the libs team for an unsafe read_line_unchecked

[Rémy Rakić @lqd]

@nomad421 that's the idea, a string is just a Vec

[Rémy Rakić @lqd]

@nomad421 You can also allocate a single string, and within a loop clear it and https://t.co/5PBRqbPS3T into it

[Rémy Rakić @lqd]

@gcouprie Ah I see. Maybe we should ask Fuchsia: it seems plausible they could be in the same situation or have their own tricks to fix it.

[Rémy Rakić @lqd]

@gcouprie if by "working from cli" you don't mean "only from the cli, i.e just the data collection part" -- and then have different visualization/UIs to use it: samply, tracy, hotspot, not-perf

[Rémy Rakić @lqd]

@RustNationUK This screenshot should say "March 26, 27, 28" right? Instead of: