Ruakij/ManagedPool
1
0
Fork 0
Code Issues 2 Pull Requests Projects Releases 1 Wiki Activity

Because of no lifetime, extra spawned objects are directly destroyed afterwards #3

New Issue
Open
opened 2019-07-08 15:01:54 +02:00 by Ruakij · 0 comments
Ruakij commented 2019-07-08 15:01:54 +02:00 (Migrated from gitea.railduction.eu)
Copy Link

Since there is no set lifetime for an extra spawned object (if more objects are spawned),
it is directly destroyed because there is no use.

There needs to be a lifetime, so the spawned object can be used again and the system can adapt to the current usage.

Since there is no set lifetime for an extra spawned object (if more objects are spawned), it is directly destroyed because there is no use. There needs to be a lifetime, so the spawned object can be used again and the system can adapt to the current usage.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
Critical
Critical
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
todo
This is todo
wontfix
This won't be fixed
No Label
bug
Critical
todo
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Ruakij
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Ruakij/ManagedPool#3
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?