Skip to content

Question: Is there a reason why pipeline is buried so far into the package? from expression.extra.result import pipeline #209

Closed

Description

@ShravanSunder

pipelines are currently in from expression.extra.result import pipeline

It seems like its a great way to chain results (or options) and i was wondering why its not exposed more easily. It seems to me like a core part of implementing result in the codebase.

Activity

  1. changed the title [-]Quesiton: Is there a reason why pipeline is buried so far into the package? from expression.extra.result import pipeline[/-] [+]Question: Is there a reason why pipeline is buried so far into the package? from expression.extra.result import pipeline[/+] on Jul 12, 2024
  2. dbrattli commented on Jul 12, 2024

    @dbrattli
    Owner

    Hi, it was added there since I was unsure if it should be added as it is in the current form (or not) i.e naming. But I guess we could now move it into the core module. The thing is that it's "container" specific so it needs to be scoped / namespaced e.g expression.result.pipeline since a Result pipeline is different from an Option pipeline.

  3. ShravanSunder commented on Jul 15, 2024

    @ShravanSunder
    Author

    I guess pipeline is also missing async compatability

  4. dbrattli commented on Aug 15, 2026

    @dbrattli
    Owner

    Closing as answered. Result and Option pipelines remain under their container-specific expression.extra.* namespaces because their semantics differ; the documentation now links both detailed APIs from the Extras and Pipeline reference pages. Async composition is tracked separately in #252.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions