Is there a reason why at(time, val) is not curried? #676

Activity

1. briancavalier commented on Feb 20, 2024

   

   briancavalier

   on Feb 20, 2024

   Member

   More actions

   Hey, @semmel. I don't think there's a reason--probably just an oversight. Sorry for the surprise. We'd happily accept a PR to curry it 😄
2. briancavalier

   added

   2.0Changes requiring a major version bump 1.x -> 2.0Changes requiring a major version bump 1.x -> 2.0

   on Mar 8, 2024
3. briancavalier

   closed this as completedin #677on Mar 8, 2024
4. briancavalier

   reopened this on Mar 8, 2024
5. TylorS commented on Mar 8, 2024

   

   TylorS

   on Mar 8, 2024

   Member

   More actions

   It may be a good idea to start brainstorming what a 2.0 might look like now that we have something deferred there. Maybe we should create an issue dedicated to it so we can discuss our ideas?

   Some off-the-cuff ideas I have:

   • Utilize the ES native Disposable type, pretty minor change, but breaking
   • Add support for asynchronous dispose, ideally with AsyncDisposable ES interface, fairly large change, but I have a number of usecases which rely on this behavior now, mostly undoing failures.
   • Add additional type parameters, could be one or both
     • E parameter to explicitly track error types
     • R parameter to allow tracking the context a Stream is running within
6. TylorS commented on Mar 9, 2024

   

   TylorS

   on Mar 9, 2024

   Member

   More actions

   I created a discussion so we can have some amount of threading and such for conversation - #680