mirror of
https://github.com/dcs-retribution/dcs-retribution.git
synced 2025-11-10 15:41:24 +00:00
769fe12159
During package planning we don't care about the details of the flight plan, just the layout (to check if the layout is threatened and we need escorts). Splitting these will allow us to reduce the amount of work that must be done in each loop of the planning phase, potentially caching attempted flight plans between loops.
31 lines
831 B
Python
31 lines
831 B
Python
from __future__ import annotations
|
|
|
|
from abc import ABC
|
|
from dataclasses import dataclass
|
|
from typing import TYPE_CHECKING, TypeVar
|
|
|
|
from game.ato.flightplans.flightplan import FlightPlan, Layout
|
|
|
|
if TYPE_CHECKING:
|
|
from ..flightwaypoint import FlightWaypoint
|
|
|
|
|
|
@dataclass(frozen=True)
|
|
class StandardLayout(Layout, ABC):
|
|
departure: FlightWaypoint
|
|
arrival: FlightWaypoint
|
|
divert: FlightWaypoint | None
|
|
bullseye: FlightWaypoint
|
|
|
|
|
|
LayoutT = TypeVar("LayoutT", bound=StandardLayout)
|
|
|
|
|
|
class StandardFlightPlan(FlightPlan[LayoutT], ABC):
|
|
"""Base type for all non-custom flight plans.
|
|
|
|
We can't reason about custom flight plans so they get special treatment, but all
|
|
others are guaranteed to have certain properties like departure and arrival points,
|
|
potentially a divert field, and a bullseye
|
|
"""
|