Starlight220
Starlight220
The case you're bringing up is indeed a mistake that can be easily made with the amount of parentheses involved. Yet I'm not sure what practical steps can be taken,...
> In my example e the last .withTimeout(1.) is "physically" attached to the immediately preceding .andThen(run(()->System.out.println("command 3e " + Timer.getFPGATimestamp()))) > BUT that is not the command that is modified....
I'm still not seeing how this is an API docs issue - it's a readability and order-of-operations issue. Adding the full content with an example etc to each decorator's docs...
> I've included a small commit that bumps our source compatibility. For sake of tracking history, that should be a separate PR.
> Although this uses two separate lists to avoid having to allocate Pair objects. This feels risky; too much chance of the state falling out of sync. Is there no...
Deprecated functionality should still work until it is removed. If functionality is broken, it should be outright removed and not just deprecated.
`SmallSet` doesn't have an `Iterator.remove` like Java?
Any reason for `pause` over `suspend` or `yield`? The latter is preferable imo
> And it's apt if async functions/continuations/coroutines (or wherever else you'd like to call them) are taught as pausable functions I strongly disagree that "pausable functions" is the term that...
With the current impl, it would suspend the entire carrier thread. Throwing could be better.