Re: Coupling in ExtentLocal

slam dunk argument for changing that API to use lambda expressions I think you misunderstood me, I am not arguing that the API should change, I am saying that enforced try-with-resources is very relevant to almost all “structured-API”s, and there should be work on it moving forward. I wrote a sim

Re: Coupling in ExtentLocal

On 04/08/2022 20:35, Holo The Sage Wolf wrote: || Some implementations of |Collection| that will always fail, some will always succeed, and some implementations (like |HashSet|) may be non-deterministic. For the uninformed this method makes sense, for each |PartitiableAction| I create some ki

Re: Coupling in ExtentLocal

It looks pretty inconsistent to have the API of the structured concurrency and of ExtentLocal have different design, especially when it seems like the 2 APIs have the same base assumptions. >From my understanding those 2 features are meant for each other. I actually agree that allowing “weak” TwR

Re: Coupling in ExtentLocal

On 7/29/22 21:37, Ron Pressler wrote: Yes, we are thinking about a "strong” TwR, but we’re busy with so many things so it might take a while. Until then, we might introduce a weaker, or less trustworthy version of ExtentLocals that uses the existing TwR and wouldn’t be used for critical things

Re: Coupling in ExtentLocal

Hi. The difference between ExtentLocals and other TwR constructs is that we’d like to use it for critical, foundational, things where we want guarantees we can rely on, and we haven’t been able to find a way to guarantee them as well as we’d like with TwR, even dynamically. Yes, we are thinkin

Re: Coupling in ExtentLocal

Hi, Thanks for the response Kasper, the reason I sent the mail to core-libs is because JDK-8263012 is assigned to "core-libs". I added loom-devs to the chain. What Andrew Haley wrote is correct, it is also correct pretty much for every implementation

Re: Coupling in ExtentLocal

On Thu, 28 Jul 2022 at 22:11, Holo The Sage Wolf wrote: > I have a question about the proposal, why not allow try-with-resources > with this API? > Hi, For Loom related questions, loom-...@openjdk.org is probably a better fit. The main problem with TWR is that it cannot guard against non-nested

Coupling in ExtentLocal

Hello core-libs devs, The ExtentLocal proposal adds a new way to transfer arguments to methods, e.g. (taken from project’s loom git