You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Question: Is there a reason why pipeline is buried so far into the package? from expression.extra.result import pipeline #209
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.
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
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.
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.
Activity
[-]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[/+]dbrattli commentedon Jul 12, 2024
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.pipelinesince a Result pipeline is different from an Option pipeline.ShravanSunder commentedon Jul 15, 2024
I guess pipeline is also missing async compatability
dbrattli commentedon Aug 15, 2026
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.