Manish Goregaokar

Detailed notes not taken. Summary: - @robertbastian suggests a static approach: - Such as what is used in Dart Intl - So that it works nicely with data slicing by...

Discussion with Eemeli on ICU4X-TC approving the spec , at a WG meeting. - @eemeli Hi, I've been working on the MF2 spec under CLDR. That is now at a...

Summary so far: * Initial design doc: https://docs.google.com/document/d/1X5qiEK1swGYMblwbBcOu1HkiZUbL4yhnekVyzPPQo-o/edit?tab=t.0#heading=h.5rulnmr2njpb * Design doc for AST representation concerns per use case: https://docs.google.com/document/d/1VaP5ZMcQLsyxRzSJI-016-e4YEN-2IPS44bwFPgxpJM/edit?tab=t.0#heading=h.mwn95cq0jjht - @robertbastian suggests a static approach: - Such as what is...

@sffc and @robertbastian and I discussed the path forward around compiletime APIs. Shane noted that the MF2.0 group has acknowledged a distinction between "link time" data loading and "runtime" data...

I suspect this is due to the `?Sized` bound and the `where Self: Sized`. Seems like a bug.

Yeah, you're right, this isn't actually related to workspaces

We could use -Zremap-cwd-prefix here: https://github.com/rust-lang/rust/pull/87320

Yeah it doesn't, i just realized: remap-cwd-prefix affects debuginfo, which is not good for build caching remap-path-prefix has the same problem

> Telling rustc where it is invoked from would require rustc to be run twice in this scenario Why so? The flag is excluded from build caching.

hmmm, interesting point that's only for successful builds, though. I wonder if there's something that can be done here (Perhaps cargo should be operating on the json output for cached...