Own canvas async work and thin NodeCanvas composite
This commit is contained in:
@@ -107,7 +107,7 @@ Current architecture mismatches that must be treated as real blockers:
|
||||
rather than thin composition/binding surfaces.
|
||||
- `App`, `Canvas`, `Node`, retained workers, and platform entrypoints still use
|
||||
global singleton reach, raw observer pointers, detached `std::thread`
|
||||
launches in several canvas/export/preview paths, and ad hoc
|
||||
launches in preview/recording paths, and ad hoc
|
||||
mutex/condition-variable ownership.
|
||||
- Modern C++23 usage exists in extracted components, especially `std::span`,
|
||||
explicit result/status objects, and a few concepts, but the live app still
|
||||
|
||||
Reference in New Issue
Block a user