> On 13 Oct 2025, at 15:31, Jige Yu <[email protected]> wrote: > > I agree with you on the importance of real-world feedback and the need to > tease apart API design discussions from observed user problems with a > specific design. My feedback is rooted in the latter: user-observed problems > with the current Structured Task Scope (STS) API's usability, specifically > its complexity for the common "concurrent AND" use case.
Hi. If you want your feedback to have an impact, please limit it to: I tried doing X, here’s what my code looks like, and here are the difficulties I’ve ran into in that code. Such feedback has typically had a very strong record of impacting decisions. Talking about problems in the abstract tends to obscure tradeoffs, and we simply do not have the bandwidth to list all the pros and all the cons of each possible design here on the mailing list (not even all the designs we’ve tried), especially when some alternative designs don’t conform with our goals and future planned work. E.g. our goal might not be to offer the cleanest possible design, but rather something that takes into consideration training programmers already familiar with existing constructs, and or something that can serve as a building block for higher-level abstractions in the future. In short, if you’ve run into some specific difficulty in actual code, show us what it is. — Ron
