You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 29, 2022. It is now read-only.
Ideally, progress objects created during a call to Task.map should participate in implicit progress composition: a map should take up 1 work unit by default, but 100 if a Progress is created using Progress.current() as a parent. This would have the benefit of working with Data reading and writing, Core Data fetches, as well as custom uses of implicit progress reporting.
Then using didAddChild to perform the 1 or 100 check. But this doesn't work, because the work in the map is done by the time the map handler returns. Maybe this is as simple as moving the override to Root and making it do something immediately. I didn't investigate it further.
The text was updated successfully, but these errors were encountered:
Lower-priority follow-up to #260, #265.
Ideally, progress objects created during a call to
Task.map
should participate in implicit progress composition: amap
should take up 1 work unit by default, but 100 if aProgress
is created usingProgress.current()
as a parent. This would have the benefit of working withData
reading and writing, Core Data fetches, as well as custom uses of implicit progress reporting.I had a prototype like:
Then using
didAddChild
to perform the 1 or 100 check. But this doesn't work, because the work in the map is done by the time themap
handler returns. Maybe this is as simple as moving the override toRoot
and making it do something immediately. I didn't investigate it further.The text was updated successfully, but these errors were encountered: