Simon Shine

1. The jumpstack semantics of `call` ties to being able to completely arithmetize the instruction. Labels are free, though, so if you don't care about jumping back, `call` can work...

@chansen: If you provide some guidance with regards to your design philosophy for `Time::Moment`, I could provide a supplemental library for dealing with `Time::Moment`-compatible durations.

Since there isn't an equivalent to `DateTime::Duration` for `Time::Moment`, you could take the difference in (seconds | days) between two `Time::Moment`s and construct a `DateTime::Duration`. Since the difference between two...

It would open up for a lot of complexity where you can't really say if time difference is correct, or even to what degree it is approximate. Making so that...

I think of `Time::Moment` as a library that gets the uncontroversial parts right by way of simplicity, and is highly efficient (as far as I remember, the motivation for the...

Sounds like the tradeoff I'd also make. I don't see any plans.

Still haven't tested `OrthodoxEasterSunday`. Tests for `WesternEasterSunday` should be sufficient. Let me know what you think about the tests for `FirstDayOfWeekInMonth`, `LastDayOfWeekInMonth` and `NthDayOfWeekInMonth`. I tried to make them somewhat...

I'll extend the example to coincide with the example given on Discord of a trustless on-chain lookup into an off-chain database, since that appears to be one minimal example (in...

>> I think a high-level description of the pipeline would help me here. > > I hope it does shed some light, does it help? Not really. What does a...

Isn't this equivalent to discarding the output of `take_while`? ```rust let (s, _) = take_while(p)(s)?; ```