K1: type1, K2: type2?
Or just allowing Union(type1, type2) to be either of type1, type2 directly?
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T282062 ZObject model: Add a key to Z3 to mark a key as optional | |||
| Open | None | T290996 Support Optional Keys in Orchestrator | |||
| Open | None | T314364 Use `data/definitions` Version of `Z983` and ` Z6984` Once We Have Unions | |||
| Open | None | T396553 definitions: Update certain keys to use union types when they are available | |||
| Open | None | T292892 Function model: Introduce a Union generic type | |||
| Open | None | T296326 Discuss How to Implement Unions | |||
| Resolved | • AAssaf | T307699 Formalize the semantics of the function model |
Event Timeline
Comment Actions
What would be the use of an untagged union? It doesn't make sense in the function model.
Comment Actions
Resetting task status from "In Progress" to "Open" as this task has been "in progress" for more than one year (see T380300). Feel free to set that status again, or rather break down into smaller subtasks.
Comment Actions
@DVrandecic Removing task assignee as this open task has been assigned for more than two years - See the email sent on 2025-05-22.
Please assign this task to yourself again if you still realistically [plan to] work on this task - it would be welcome!
If this task has been resolved in the meantime, or should not be worked on by anybody ("declined"), please update its task status via "Add Action… 🡒 Change Status".
Also see https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup for tips how to best manage your individual work in Phabricator. Thanks!