Alexander Sepity

I [wrote](https://github.com/ggez/ggez/pull/362) an experimental facade to `gfx_glyph` for `ggez`; once it's sort of finalized (i.e., has been released for at least one version and gathered some feedback), the plan is...

> From an api perspective, I see no meaningful difference between an "exclusive system" and a system that manually claims every resource. As I've said in https://github.com/bevyengine/bevy/pull/1144#issuecomment-755655210: > There is:...

I am talking about the actual implementation, again. When a systems' graph is scheduled, exclusive systems must necessarily be placed at *exact spots* wrt blocks of *specific* parallelizable systems, otherwise...

> Right, because otherwise we're spinning our wheels constantly checking a condition (can this exclusive system run) that will never be met. No, that's not it. Exclusive systems can change...

> The system tasks are spawned before we know if any system can run, and that borrow keeps us from updating their archetype component access. That's not how the systems...

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

[Rendered](https://github.com/bevyengine/rfcs/blob/9623eaa041aba2c8e227479166dcf71080753a21/rfcs/2736-system_builder_syntax.md).

"Future work" refers to a subsection of the RFC where you note down stuff that could happen after this RFC is accepted and implemented. I don't think label properties are...

> @DJMcNab, you ran into some issues with yeeting .exclusive_system though right? That was a while ago, I've fixed that. This breaks it again; haven't had the time to try...

It *might* be possible to hook this up via `gfx_glyph`'s [`GlyphPositioner`](https://docs.rs/gfx_glyph/0/gfx_glyph/trait.GlyphPositioner.html) (I've been eyeing it for fully-animated text). At very least, right-to-left ordering itself shouldn't be too hard to implement;...