Jay Oster

> documentation is always going to be useful to someone. ;-) This is probably the most compelling reason to continually write about and document the lay-of-the-land. Even if it all...

I've been comparing against `parking_lot::RwLock`. That implementation is admittedly very complex. And in all honesty, I'm not an expert in task scheduling. Fairness is mostly achieved by scheduling tasks in...

Write-preferring locks do not starve readers, at least not in the same sense that read-preferring locks can guarantee writers will be unable to acquire a lock _at all_ in the...

Ok, this can be done with NVAPI: https://gist.github.com/rickbrew/10e5c0fa3593ceb6f03766914f43a0c6 There is a Rust crate for it, but it doesn't have any of the DRS stuff.

I was hopeful that the linked PR would fix this, but it does not. I put the CozetteVector.ttf into an egui hello world with and without the patch applied. The...

> it could make more sense to put a layer of abstraction between `epaint` and `ab_glyph` such that there's a trait that can be implemented by clients to provide a...

I'm talking about abstractions leaking implementation details. :) There's no reason that someone who wants to put text into the UI should have to know anything about texture atlases. Let...

> The above isn't real, and definitely isn't correct, but the idea would be that _any_ font implementation should be able to easily implement the above primitives, be that `ab_glyph`...

I think some specification of the meta language syntax is still important even if it is not EBNF. For instance when I wrote a syntax definition for Sublime Text, I...

Closing this is the right thing to do. I can’t comment on how it compares to the `#[property(path = "…")]` attribute. But as long as it supports grouping the same...