In the top of src/Aztecs.ECS.hs
-- ==== Access
-- An `Access` can be queued for full access to the `World`, after a system is complete.
-- `Access` allows for spawning, inserting, and removing components.
--
-- > setup :: System () ()
-- > setup = S.queue . const . A.spawn_ $ bundle (Position 0) <> bundle (Velocity 1)
specifically
S.queue . const . A.spawn_ $ bundle ...
While I don't see any S.queue function anywhere in the code. I'm guessing this documentation is leftover from an older version of the API?
All the examples in the examples repo appear to run Access directly from main, nothing looks like a System that emits a queued Access.
In the top of
src/Aztecs.ECS.hsspecifically
While I don't see any
S.queuefunction anywhere in the code. I'm guessing this documentation is leftover from an older version of the API?All the examples in the examples repo appear to run
Accessdirectly frommain, nothing looks like aSystemthat emits a queuedAccess.