Tushar

> @tusharsnx had some good rationale for only supporting the ITU T.418 format for underline colors I remember blocking the sending of CSI-58 with `;` because it can have [unexpected...

> For app devs (which includes zellij), I would recommend against using ITU sequences in any format unless you've somehow verified that the terminal actually supports those sequence. I agree...

Seems like #444 (#781) broke `io.mkdirP`, particularly with the removal of [these lines](https://github.com/actions/toolkit/commit/15fef781713c318fceb3febc85ab153bfbb5187c#diff-861188803429d5c83ae5ebfe7c781fa222713f0562db5d851e7817ee6c1ca7fcL93-L102). `fs.stat`'ing throws no error when the drive exists. So the `default:` case would've gracefully handled all *EPERM*...

Do we have any updates on this?

Atlas engine caches all the glyphs it renders, so you are only really paying the rendering cost on first use of any glyph. Later rendering just copies the cached glyph,...

@lhecker, what you said makes sense; we do need glyph bounds in advance but `GetGlyphRunWorldBounds` doesn't work well with SVG/COLRv1. I actually saw MSEdge and Chrome supporting the 3D emojis,...

Would it be good enough to split `useExhaustiveDependencies` into two buckets, one with *"[myFunc] changes on every re-render and should not be used as a hook dependency"* warning, and another...

We should also think about the DX as not all components can be memoized (due to their implementation). React compiler can statically check for this. I'm proposing the following: 1....

> personally think it will be confusing to introduce such an option, if I see such an option I will understand it as something to do with React.memo. Yes, it...

> shall we close this issue please? I think we should wait for some time. The plans around how `useEffect` will change due to the compiler are still unclear. There...