feat: engine initialization stage rewrite #14
Labels
No labels
Blocked
ByBug
Blocked
ByDependency
Blocked
ByMissingFeature
Bug
Accepted
Bug
Fixed
Bug
In Progress
Bug
Invalid
Bug
ItWorksOnMyMachine
Bug
MoreInvestigation
Bug
New
Empty
FeatureRequest
Accepted
FeatureRequest
Implemented
FeatureRequest
In Progress
FeatureRequest
Invalid
FeatureRequest
New
FeatureRequest
PartiallyImplemented
FeatureRequest
WontAdd
Important
PR
BranchMerge
PR
BugFix
PR
Documentation
PR
FeatureAddition
PR
Miscellaneous
PR
Mixed
PR
New
PR
Tests
PR
Update
Roadmap
Stale
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Reference: StarOpenSource/Engine#14
Loading…
Reference in a new issue
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?
Feature description
The current engine initialization process is a bit over the place and quite unstable. Little things changing in the source have often enough caused headaches and engine initialization failures. It may be time to rework how the engine initializes.
The goal however is to not impact the engine's runtime operations or how the engine should be initialized. Only internal stuff that applications and games can't/should never touch is allowed to be changed.
Feature implementation
There are 101 ways of rewriting the engine, and I won't list 'em all.
Feature alternatives
Leaving it as-is. The engine initialization process however is... weird, as described above. Doing so would be a not very smart idea.